GET /v1/companies

Lists the companies your token can read, with the size and span of each one's history. Use it to discover the domains you can pass to /v1/events. It takes no parameters.

curl -H "Authorization: Bearer YOUR_TOKEN" \
  "https://api.docsignal.app/v1/companies"

{
  "companies": [
    {
      "domain": "linear.app",
      "name": "Linear",
      "organization_id": "ogn_01ARZ3NDEKTSV4RRFFQ69G5FAV",
      "category": "product-led-saas",
      "shipped_from": "2019-04-11",
      "observed_from": "2026-07-19T00:00:00Z",
      "events": 672,
      "dated_events": 613,
      "structure_updated_at": "2026-04-01"
    }
  ]
}

Field	Meaning
`domain`	What to pass in `domains` on `/v1/events`.
`name`	The company's display name.
`organization_id`	Stable ID in the canonical organization graph. Additive; use it to join to `/v1/organizations` and `/v1/products`.
`category`	What kind of company it is, shared across the panel so peers are comparable.
`shipped_from`	The earliest ship date we hold for this company.
`observed_from`	When we began observing it.
`events`	Total events we hold.
`dated_events`	How many of those carry a `shipped_at`.
`structure_updated_at`	Latest effective relationship or geography boundary in the active organization subtree.

observed_from is when tracking began for that company. History starts there.

Aliases

Some companies publish under more than one domain, and the alias resolves to the canonical one. devin.ai resolves to cognition.ai, claude.com to anthropic.com. The query block in the response tells you which domain your request actually resolved to.

Domains remain the v1 lookup and filtering interface. organization_id adds a stable identity that survives domain and name changes; existing clients can ignore it.

Aliases​

Aliases