> ## Documentation Index
> Fetch the complete documentation index at: https://docs.api.tamtam.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Create a new hire signal

> A search for people who have just taken a role matching one of your personas, at any company or at named companies, collected as leads. A new hire is the moment a buyer's priorities are most open.

The role can come from either side, and the signal needs one of them: `persona_ids` (one search per persona per sweep, carrying that persona's titles, countries and seniority) or the titles stated directly in `job_titles_includes`. The two compose: where a persona speaks it wins; where it is silent the lane's own axis stands, so firmographics that belong to one lane (employer size, employer HQ, industries, seniority) go here rather than into a persona everyone else reuses.

Cost when it runs: every profile read costs one credit, up to `max_profiles_per_sweep` per persona.

**Creating a signal starts nothing and bills nothing.** A signal runs only when a lead generation program picks it: [Start a lead generation run](/api-reference/signals/start-lead-generation-run) sweeps it now and records a program you can put on a schedule under Settings > Signals > Lead generation. [List signals](/api-reference/signals/list-signals) reports `used_by_program_count` per signal; zero means it is defined and never runs. List first, so you do not create a second signal over a question you already ask: duplicates bill twice and split the leads across two names.



## OpenAPI

````yaml /reference/openapi.yaml post /v2/new-hire-signals
openapi: 3.1.0
info:
  title: Tamtam Public API
  version: 2.0.0
servers:
  - url: https://api.tamtam.ai/api
security: []
paths:
  /v2/new-hire-signals:
    post:
      tags:
        - Signals
      summary: Create a new hire signal
      description: >-
        A search for people who have just taken a role matching one of your
        personas, at any company or at named companies, collected as leads. A
        new hire is the moment a buyer's priorities are most open.


        The role can come from either side, and the signal needs one of them:
        `persona_ids` (one search per persona per sweep, carrying that persona's
        titles, countries and seniority) or the titles stated directly in
        `job_titles_includes`. The two compose: where a persona speaks it wins;
        where it is silent the lane's own axis stands, so firmographics that
        belong to one lane (employer size, employer HQ, industries, seniority)
        go here rather than into a persona everyone else reuses.


        Cost when it runs: every profile read costs one credit, up to
        `max_profiles_per_sweep` per persona.


        **Creating a signal starts nothing and bills nothing.** A signal runs
        only when a lead generation program picks it: [Start a lead generation
        run](/api-reference/signals/start-lead-generation-run) sweeps it now and
        records a program you can put on a schedule under Settings > Signals >
        Lead generation. [List signals](/api-reference/signals/list-signals)
        reports `used_by_program_count` per signal; zero means it is defined and
        never runs. List first, so you do not create a second signal over a
        question you already ask: duplicates bill twice and split the leads
        across two names.
      operationId: create-new-hire-signal
      parameters:
        - description: >-
            Target account UUID. Required for staff callers; ignored for
            customer API keys.
          explode: false
          in: query
          name: account_id
          schema:
            description: >-
              Target account UUID. Required for staff callers; ignored for
              customer API keys.
            type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/NewHireSignalBody'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SignalCreatedDto'
          description: OK
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ErrorModel'
          description: Error
      security:
        - apikeyAuth: []
        - bearerAuth: []
components:
  schemas:
    NewHireSignalBody:
      additionalProperties: false
      properties:
        canonical_job_title_ids:
          description: >-
            Canonical job-title UUIDs, at most 50. A union with
            job_titles_includes, and it also counts as naming the role.
          items:
            type: string
          maxItems: 50
          type:
            - array
            - 'null'
        company_headcounts:
          description: >-
            Size bands of the NEW employer, as LinkedIn letter codes: A
            (self-employed), B (1-10), C (11-50), D (51-200), E (201-500), F
            (501-1,000), G (1,001-5,000), H (5,001-10,000), I (10,001+).
          items:
            type: string
          type:
            - array
            - 'null'
        company_hq_countries:
          description: Two-letter country codes where the NEW employer is headquartered.
          items:
            type: string
          type:
            - array
            - 'null'
        company_linkedin_ids:
          description: >-
            Numeric LinkedIn company IDs, at most 100: watch hires INTO these
            companies only. Omit to watch hires anywhere.
          items:
            type: string
          maxItems: 100
          type:
            - array
            - 'null'
        countries:
          description: >-
            Two-letter country codes narrowing a persona that names no country
            of its own: where the PERSON is.
          items:
            type: string
          type:
            - array
            - 'null'
        industry_ids:
          description: Industry UUIDs the new employer has to be in, at most 25.
          items:
            type: string
          maxItems: 25
          type:
            - array
            - 'null'
        is_enabled:
          description: Defaults to true.
          type: boolean
        job_titles_excludes:
          description: Job titles to drop, at most 50. Narrows the lane; never names it.
          items:
            type: string
          maxItems: 50
          type:
            - array
            - 'null'
        job_titles_includes:
          description: >-
            Job titles to watch, stated directly, at most 50. Either this or
            persona_ids has to name the role.
          items:
            type: string
          maxItems: 50
          type:
            - array
            - 'null'
        location_geo_ids:
          description: >-
            LinkedIn geo IDs where the PERSON is, at most 25: a region, city or
            metro a country code cannot express.
          items:
            type: string
          maxItems: 25
          type:
            - array
            - 'null'
        max_profiles_per_sweep:
          description: >-
            Profiles read per persona per sweep. Defaults to 100. The cost dial:
            each profile read costs one credit.
          format: int32
          maximum: 500
          minimum: 1
          type: integer
        name:
          description: >-
            Short label, unique in the account. Name it after the hire it
            watches, e.g. 'New RevOps leaders'.
          minLength: 1
          type: string
        persona_ids:
          description: >-
            The roles a new hire has to match, at most 20. Required unless
            job_titles_includes or canonical_job_title_ids names the role
            instead.
          items:
            type: string
          maxItems: 20
          type:
            - array
            - 'null'
        seniority_levels:
          description: >-
            Seniority levels to keep: In Training, Entry Level, Senior,
            Strategic, Entry Level Manager, Experienced Manager, Vice President,
            Director, CXO, Owner / Partner. Read from the title after results
            come back, so it narrows who is kept, not who is paid for.
          items:
            type: string
          type:
            - array
            - 'null'
      required:
        - name
      type: object
    SignalCreatedDto:
      additionalProperties: false
      properties:
        id:
          type: string
        is_enabled:
          type: boolean
        kind:
          description: >-
            The kind, as List signals reports it and as a lead generation run
            takes it.
          type: string
        name:
          type: string
        used_by_program_count:
          description: >-
            Always 0 on creation: a signal runs only when a lead generation
            program picks it.
          format: int64
          type: integer
      required:
        - kind
        - id
        - name
        - is_enabled
        - used_by_program_count
      type: object
    ErrorModel:
      additionalProperties: false
      properties:
        detail:
          description: >-
            A human-readable explanation specific to this occurrence of the
            problem.
          examples:
            - Property foo is required but is missing.
          type: string
        errors:
          description: Optional list of individual error details
          items:
            $ref: '#/components/schemas/ErrorDetail'
          type:
            - array
            - 'null'
        instance:
          description: >-
            A URI reference that identifies the specific occurrence of the
            problem.
          examples:
            - https://example.com/error-log/abc123
          format: uri
          type: string
        status:
          description: HTTP status code
          examples:
            - 400
          format: int64
          type: integer
        title:
          description: >-
            A short, human-readable summary of the problem type. This value
            should not change between occurrences of the error.
          examples:
            - Bad Request
          type: string
        type:
          default: about:blank
          description: A URI reference to human-readable documentation for the error.
          examples:
            - https://example.com/errors/example
          format: uri
          type: string
      type: object
    ErrorDetail:
      additionalProperties: false
      properties:
        location:
          description: >-
            Where the error occurred, e.g. 'body.items[3].tags' or
            'path.thing-id'
          type: string
        message:
          description: Error message text
          type: string
        value:
          description: The value at the given location
      type: object
  securitySchemes:
    apikeyAuth:
      description: Account API key passed in the Authorization header
      in: header
      name: Authorization
      type: apiKey
    bearerAuth:
      description: Bearer JWT obtained via the OAuth 2.1 authorization flow
      scheme: bearer
      type: http

````