> ## 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 an ex-customer move signal > The people who once worked at one of your customers, match one of your personas, and work somewhere else now, collected as leads. A person who used the product at a previous employer is a warm door into the new one. `persona_ids` does both halves of who: the personas' job titles become the search's current-title filter, and the same personas judge the titles that come back. The population is your customers, chosen one of three ways: the companies your CRM has won deals with (`include_current_customers`, default), optionally the ones it later lost a deal with too (`include_former_customers`), or one list instead (`companies_list_id` or `hubspot_list_id`), which makes the two switches moot. Cost when it runs: every profile read costs one credit, up to `max_movers_per_sweep`. **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/past-company-move-signals openapi: 3.1.0 info: title: Tamtam Public API version: 2.0.0 servers: - url: https://api.tamtam.ai/api security: [] paths: /v2/past-company-move-signals: post: tags: - Signals summary: Create an ex-customer move signal description: >- The people who once worked at one of your customers, match one of your personas, and work somewhere else now, collected as leads. A person who used the product at a previous employer is a warm door into the new one. `persona_ids` does both halves of who: the personas' job titles become the search's current-title filter, and the same personas judge the titles that come back. The population is your customers, chosen one of three ways: the companies your CRM has won deals with (`include_current_customers`, default), optionally the ones it later lost a deal with too (`include_former_customers`), or one list instead (`companies_list_id` or `hubspot_list_id`), which makes the two switches moot. Cost when it runs: every profile read costs one credit, up to `max_movers_per_sweep`. **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-past-company-move-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/PastCompanyMoveSignalBody' 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: PastCompanyMoveSignalBody: additionalProperties: false properties: companies_list_id: description: >- List population: one of your companies lists to search instead of the CRM. Pass this OR hubspot_list_id, never both. type: string 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' countries: description: Two-letter country codes where the PERSON is now. items: type: string type: - array - 'null' hubspot_list_id: description: >- List population: the id of a live HubSpot list to search instead of the CRM's won deals, resolved at every sweep. Pass this OR companies_list_id, never both. Salesforce has no live list read: import the list into a companies list first. type: string include_current_customers: description: >- CRM population: search the companies your CRM has won deals with. Defaults to true. Ignored when a list is given. type: boolean include_former_customers: description: >- CRM population: also search won companies the CRM later lost a deal with, a proxy for churned customers. Defaults to false. Ignored when a list is given. type: boolean 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 location_geo_ids: description: LinkedIn geo IDs where the PERSON is, at most 25. items: type: string maxItems: 25 type: - array - 'null' max_movers_per_sweep: description: >- Profiles read 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, e.g. 'Ex-customer ops leaders'. minLength: 1 type: string persona_ids: description: >- One to ten personas: who the search looks for and who it keeps. The personas' job titles become the search's current-title filter. items: type: string maxItems: 10 minItems: 1 type: - array - 'null' required: - name - persona_ids 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 ````