API DOCUMENTATION / COMPANY DATA
Company data
Read the compact company registry and understand canonical IDs, merge redirects, and company-scoped job listing.
Company record shape
{
"company_id": "000edf59-a91d-4ab2-970f-a9c25f46060a",
"name": "Salesforce",
"country": null,
"status": "active"
}A live response from October 8, 2026. The registry covers the companies behind published jobs: 2,874 companies on October 8, 2026 (2,810 active, 64 merged into another record, which redirect). Country is null for every company for now. The company DTO contains only company_id, name, nullable country, and status (active, retired, or merged).
Company identity differs from employer text
A canonical company UUID identifies the company registry record. It is not a domain, discovery key, or a guarantee that every employer string has been matched. A job’s nullable company_id and its employer-name field are distinct.
Merged companies redirect
A merged company ID responds with HTTP 308 and a Location header pointing to the current ID. The redirect response is bodyless. Missing IDs map to 404; unresolved merge cycles or unavailable projection conditions can map to 503.
Company job listings
GET /v1/companies/{companyId}/jobs is available with an API key. It pages the jobs projection for a canonical company ID and redirects a merged company to its replacement. Projection and company lookup failures can return 503.
Do not infer enrichment
The company registry contract is the four fields above. No broader company-enrichment, firmographic, contact, or hierarchy fields are established by this public DTO.
Continue in the reference
Check related request behavior before you build.
View route status and methods Discuss API requirements