Company data API
Retrieve the companies, change events and review cases in your CompanyDelta workspace. Give your application the context to show what changed, where it came from and who needs to review it.
Company records from the data provider. One workspace for your monitoring workflow.
{
"type": "ownership",
"title": "Recorded holding increased",
"previous": "40%",
"current": "65%",
"source": "Illustrative registry record",
"filed": "2026-09-09",
"effective": "2026-09-04",
"sample": 1
}Keep the record and the review connected
A company profile answers who you are dealing with. A recorded change helps your team decide whether that relationship needs another look. CompanyDelta brings both into the same workspace, with review cases your application can retrieve.
Show an ownership or company-status change beside the supplier your team already knows. Match the CompanyDelta identifier to your internal supplier reference and link to the supporting review.
Supplier intelligence →Retrieve changes after the initial company review. Route relevant events into your own queue, preserving the source, previous value and unresolved questions for the person investigating them.
Ongoing company verification →Use recorded field changes to propose an update in your CRM or supplier system. Your integration decides how fields map and which changes require approval before anything is written.
Company data management →From request to review
In this example, a recorded shareholding moves from 40% to 65%. The API event preserves the two values, the source description and the relevant dates. Your software can use the event identifier to avoid creating the same internal task twice.
The filing date, effective date and detection time describe different things. Retain those distinctions when you show a timeline or decide which events belong in a review period.
Explore the event catalogue →Illustrative company and values. This example does not query a live registry.
curl 'https://companydelta.com/api/v1/events?limit=25' \
-H "Authorization: Bearer $COMPANYDELTA_API_KEY"{
"data": [{
"id": "sample-event-01",
"company": "sample-company-01",
"type": "ownership",
"previous": "40%",
"current": "65%",
"source": "Illustrative registry record",
"source_url": "",
"filed": "2026-09-09",
"effective": "2026-09-04",
"detected": "2026-09-12T09:00:00Z",
"sample": 1
}],
"next_cursor": null
}An active paid workspace and a scoped API key are required. Public website access does not grant access to any workspace data.
Know what each endpoint returns
The company information API reads records already held in your workspace. Available fields depend on the source connection, the company and the records collected. A missing field should remain visible as a gap in your workflow.
| Resource | What your application receives | How to use it |
|---|---|---|
GET /api/v1/companies | Saved company identifiers, country, monitoring state, watch categories and the stored record. | Link a legal entity to your customer, supplier or partner record. |
GET /api/v1/events | Recorded changes, previous/current values, source details, dates and sample indicators. | Show the change history or create a task in your own application. |
GET /api/v1/cases | Review cases with event references, status, assignee and saved notes. | Keep visibility into the investigation associated with an event. |
POST /api/v1/events | An accepted event identifier, or the existing identifier for a duplicate external event. | Bring an authorised source pipeline into CompanyDelta workflows. |
List endpoints support cursor pagination. The current API does not provide a global company-search endpoint or a separate public endpoint for every financial and ownership field.
Start with one useful workflow
Identify the countries, legal entities and change categories that matter. Check company and corporate linkage coverage, then confirm the fields and source connection for your intended workflow.
Owners and admins can create a key in the online platform. Use read access for retrieval and separate credentials for event ingestion or scheduled job execution. Store credentials in your server environment.
Retrieve a first page, follow the returned cursor and map company identifiers to your system. Test an empty result, a missing source link and a revoked key as well as a successful response.
Use API retrieval when your application controls the request. Add webhooks when your receiver should be notified of recorded events. Agree how source checks and queued delivery jobs will run.
An API your team can evaluate
For an enterprise pilot, measure whether your companies can be matched, whether relevant changes arrive with usable evidence and whether the receiving team can complete a review. Raw record counts alone do not establish the value of a monitoring integration.
Live registry collection and external access need configuration. The private workspace can already be used to inspect sample records and API-key controls.
Explore the online platform →API questions
It is a workspace API for retrieving saved companies, company-change events and review cases, and for accepting events from an authorised data pipeline. It connects the records in your CompanyDelta workspace to your own application.
No. The current public API routes list records already saved in the selected workspace. Registry search and matching are available through the configured workspace experience; the list endpoint is not a global company-search API.
The companies endpoint includes the stored company record, and events can describe ownership or financial-filing changes. The exact fields depend on available source records and configuration. There is no promise of a complete ownership graph or financial statement for every company.
A key belongs to one workspace and carries selected scopes. Read access permits retrieval; events:write permits event ingestion; jobs:run permits job execution. Keys have an expiry, can be revoked and are shown only when created. The site's separate access rules still apply.
No real-time guarantee is made. Active paid workspaces are processed by the recurring scheduler, but detection still depends on source availability, successful collection and receiver availability.
List endpoints return data and next_cursor. Request up to 100 records per page and pass a returned cursor into the next request until next_cursor is null. The cursor is an identifier for traversal, not a timestamp or a substitute for a chronological event feed.
Your engineering team can build an integration that reads CompanyDelta records and uses your destination system's API. A native connector or automatic writeback is not included in the current product. Field mapping and approval rules belong in that integration.
Discuss the intended display, users, retention and redistribution with CompanyDelta before launch. Technical API access does not itself grant redistribution rights. An embedded offering needs agreed commercial terms and a tested access arrangement.
Authorised users can explore the sample workspace, create scoped keys and inspect saved companies, events and reviews. The documentation describes the implemented routes. A live-data pilot also requires a source connection and an approved access path for external clients.
Review the API contract, then evaluate a focused portfolio workflow.