> ## 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 news signal > A standing news search whose articles an AI scores against your own use-cases, turning the relevant ones into leads. Two shapes, and the shape follows the target you pass. **Discovery**: pass `queries`, and each sweep searches the whole news for those themes, finding companies you do not follow yet. **Watch**: pass `companies_list_id` or `contacts_list_id` instead, and each sweep reads the news of the companies on that list. Exactly one target; queries plus a list, or both lists, is a 422. `use_cases` is the whole relevance definition: an article becomes a lead when it falls into at least one, judged on that use-case's own prompt. Write each prompt as a test the article must pass, in your words, and say what to extract. Cost when it runs: one credit per article judged, up to `max_articles_per_query` per query 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/news-content-signals openapi: 3.1.0 info: title: Tamtam Public API version: 2.0.0 servers: - url: https://api.tamtam.ai/api security: [] paths: /v2/news-content-signals: post: tags: - Signals summary: Create a news signal description: >- A standing news search whose articles an AI scores against your own use-cases, turning the relevant ones into leads. Two shapes, and the shape follows the target you pass. **Discovery**: pass `queries`, and each sweep searches the whole news for those themes, finding companies you do not follow yet. **Watch**: pass `companies_list_id` or `contacts_list_id` instead, and each sweep reads the news of the companies on that list. Exactly one target; queries plus a list, or both lists, is a 422. `use_cases` is the whole relevance definition: an article becomes a lead when it falls into at least one, judged on that use-case's own prompt. Write each prompt as a test the article must pass, in your words, and say what to extract. Cost when it runs: one credit per article judged, up to `max_articles_per_query` per query 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-news-content-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/NewsContentSignalBody' 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: NewsContentSignalBody: additionalProperties: false properties: companies_list_id: description: >- WATCH shape: a companies list whose companies' news to read. Pass this OR queries, never both. type: string contacts_list_id: description: >- WATCH shape: a contacts list whose companies' news to read. Pass this OR queries, never both. type: string include_domains: description: >- DISCOVERY shape only: bare hostnames to trust, e.g. techcrunch.com. Omit for the whole web. items: type: string type: - array - 'null' is_enabled: description: Defaults to true. type: boolean max_articles_per_query: description: >- Articles judged per query per sweep: the cost dial, one credit per judged article. Omit for the default. format: int32 minimum: 1 type: integer max_companies_per_sweep: description: >- WATCH shape only: how many companies of the list to read per sweep. Omit for the default. format: int32 minimum: 1 type: integer name: description: >- Short label, unique in the account. Name it after the question, e.g. 'Series B in fintech'. minLength: 1 type: string queries: description: >- DISCOVERY shape: short search themes, each run as its own search per sweep, finding companies you do not follow yet. Pass this OR a list id, never both. items: type: string type: - array - 'null' search_keywords: description: >- WATCH shape only: narrow the search to company AND one of these topics. Omit to read everything stored for the company. items: type: string type: - array - 'null' time_filter: description: How far back each sweep looks. Defaults to last_week. enum: - last_day - last_week - last_month - last_3_months type: string use_cases: description: >- One to ten use-cases: the whole relevance definition. An article is relevant when it falls into at least one, judged on that use-case's own prompt. items: $ref: '#/components/schemas/NewsSignalUseCaseDto' maxItems: 10 minItems: 1 type: - array - 'null' required: - name - use_cases 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 NewsSignalUseCaseDto: additionalProperties: false properties: name: description: Chip label shown on every lead, unique within the signal. minLength: 1 type: string prompt: description: >- The test an article must pass to fall into this use-case, and what to extract from it. minLength: 1 type: string required: - name - prompt 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 ````