Signal
News event stream
- Coverage
- US / CN / JP
- Billing
- 1 cr / call
One row per event: multiple reports of the same event are merged into one representative event, first_reported / sources state when it was first reported and which sources covered it, and the merged duplicate reports do not appear as separate rows. Rows carry no public id. The endpoint provides only a cross-source event summary and a link to each source article; it does not provide the body text of any single article.
Covers three markets, US / CN / JP. Most events are macro, political or geopolitical and are not tied to any company; query them by theme / signal_type, or omit the filters to retrieve the latest events.
Query parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| ticker | string | optional | At most 10, comma separated; omit it to skip company filtering. One event can be associated with several companies, so when several tickers are passed an event is returned if it matches any of them. |
| signal_type | string | optional | Event type, multiple values allowed, comma-separated (product_launch / earnings / regulatory_action / ma / exec_change… full set in OpenAPI). |
| theme | string | optional | Theme label; exact, case-sensitive match; accepts comma-separated values and returns a row when any value matches. Values are natural-language phrases rather than slugs (for example artificial intelligence, geopolitics, energy transition, and AI infrastructure buildout). Themes are generated as storylines are synthesized and are not a closed enum. |
| limit | int | optional | Maximum 10. Default 10. |
| page | int | optional | Starts at 1. Default 1. |
Sorted event_time desc, first_reported desc. Paged with limit and page (pages start at 1); fewer rows than limit means the last page.
Response fields
| Field | Type | Description |
|---|---|---|
| signal_type | string | News-event type (full enum in OpenAPI). It is independent from the disclosure-event event_type used by /events*; enum values can share a name while carrying different meanings, such as ma / exec_change. |
| summary | string | Cross-source event summary (currently mostly English, with a small number of Chinese rows); contains no body text from any source article |
| primary_entity_name | string | Name of the event subject (may be a company, or a person / organization / country) |
| object_name | string | Name of the event object (the acquired party, the regulated party, and so on) |
| tickers | string[] | Associated company codes; may be an empty array. Because one event can involve multiple companies, this endpoint returns a tickers array and has no row-level scalar ticker. Only canonical US / CN / JP codes are returned, and they can be passed directly to other ticker-scoped endpoints. Out-of-scope companies involved in the event are not represented in the array. |
| themes | string[] | Theme tags (storylines synthesized across events, may be an empty array) |
| event_time | datetime | When the event occurred (not when it was persisted) |
| first_reported | datetime | Report time of the earliest source |
| sources | object[] | source_name / source_url / reported_at for each source (deep link to the source article) |
No key yet? Create one under API Keys — it is shown once, so store it where your shell can read it. Connecting an agent over MCP instead? That signs in through the browser and needs no key at all.
Authentication, conventions, rate limits and error shapes are the same for every endpoint — they live on REST API.