Open a company review
Your receiver can turn a director, ownership or legal-status event into a task. Use the company identifier to find the responsible relationship owner and attach the event for review.
Company verification workflows →Company monitoring webhooks
Turn a company change into the next task.
Send recorded company events to your own HTTPS endpoint. Bring the changed values and source into a review queue, notification service or workflow your team already uses.
Signed event payloads. Visible delivery status. Your receiver controls the response.
Event → your workflowIllustrative delivery
- 01Ownership event recorded
Northstar · Recorded holding 40% → 65%
- 02Delivery queued
Event and source attached to the message
- 03Receiver accepts the event
Signature checked · Delivery ID retained
- 04Your workflow opens a task
Assigned for ownership review
Your receiver implements the final action. No external task is created by this example.
Put a recorded change in front of the right person
Connect the event to a useful response.
Webhooks are useful when your system should receive an event without repeatedly asking whether new records exist. CompanyDelta queues a message when an event is recorded; a delivery job sends that message to your enabled destination.
Notify the supplier team
Connect your receiver to the notification channel procurement uses. Apply your own routing rules so the relevant team sees the changed record and the question it should investigate.
Supplier monitoring workflows →Bring filings into an analyst queue
Use a financial-filing event to prompt a statement review. Retrieve the available financial information, check the reporting period and assign a comparison task through your own workflow.
Financial filing workflows →A compact message with context
Receive the change, then decide what follows.
The current webhook envelope is company.changed. Its change.field contains the exact Global Database Watch API identifier, alongside the company reference, changed values and source details.
This sample message describes a recorded holding increase. Your receiver could use it to open an ownership review. The message itself is not a verified conclusion about beneficial ownership or an instruction to restrict a supplier.
See all 35 Watch API fields →The outbound webhook and the API ingestion request use different field names. Use the correct format for the direction of the integration.
POST · Illustrative webhook body
{
"id": "sample-event-01",
"type": "company.changed",
"occurred_at": "2026-09-16T09:00:00Z",
"workspace_id": "sample-workspace-01",
"company": {
"id": "sample-company-01",
"name": "Northstar Manufacturing Ltd"
},
"change": {
"field": "shareholder.holding",
"label": "New shareholder",
"status": "UPDATE",
"old_value": "40%",
"new_value": "65%"
},
"source": {
"name": "Global Database Watch API",
"url": "https://api.globaldatabase.com/docs/v2/#watch-companies-api"
}
}Invented company and identifiers. The exact event field lets your receiver apply field-level routing.
Delivery your engineer can reason about
Know what was queued, accepted or failed.
A useful webhook integration includes more than a destination URL. It needs authentication of the message, visible failures and a receiver that can safely handle the same delivery again.
| Behaviour | What CompanyDelta does | What your receiver should do |
|---|---|---|
| Message signing | Sends an HMAC-SHA256 signature, timestamp and delivery identifier in request headers. | Verify the signature over the timestamp and exact raw request body before parsing or acting. |
| Acceptance | Marks a delivery successful after a 2xx response. | Durably record or queue the accepted event, then respond promptly. |
| Failures and retries | Records failures and a next eligible attempt, with up to five attempts per delivery. | Inspect failed deliveries and handle repeated delivery IDs without repeating the business action. |
| Timing | Sends queued events when a job or an authorised retry runs. | Agree how jobs are scheduled and monitor the delay that matters to your workflow. |
| Routing | Queues new events for enabled workspace destinations. | Filter categories and company identifiers in your receiver; destination-specific event filters are not currently configured. |
Automatic jobs process eligible company checks and queued notifications. The workspace shows the last completed run; source availability and portfolio size affect timing. Webhook delivery is not a guarantee of immediate registry detection, exactly-once delivery or event ordering.
From destination to working process
Test one event all the way through.
Prepare your receiving endpoint
Use a public HTTPS URL without credentials in the address, a custom port or a redirect. The receiver must validate the message and map the company reference to the correct internal record.
Add the destination in CompanyDelta
An owner or admin creates the webhook destination in the workspace. Save the signing secret when it is shown and keep it in your receiver's secure configuration.
Check the accepted and failed paths
Use an illustrative event first. Confirm that a valid message enters your queue, an invalid signature is rejected and a repeated delivery does not create a second task. Avoid sending sample events into a production approval flow.
Agree the operational handoff
Choose who maintains source checks, scheduled jobs and receiver health. A delivery marked accepted means your server acknowledged it; your own logs must show whether the downstream case or notification was created.
Choose the right connection
Use the API for retrieval. Webhooks for notification.
The two work together. A webhook can tell your application that a recorded event exists. The API lets it retrieve the corresponding saved records and review cases, or reconcile the wider workspace.
For a team that wants to investigate in the browser, the online platform keeps company records, review assignments and decisions together.
Bring your own destination logic
A CRM, ticketing tool or messaging platform may require a particular payload and authentication format. Your receiver translates the CompanyDelta event into that format and applies your policies.
Native Salesforce, HubSpot, Slack or ERP connectors are not included in this release. A general webhook endpoint does not automatically create a working connection to those products.
Inspect the headers and signing rules →Webhook questions
Before your first delivery.
What is a company monitoring webhook?
It is an HTTP message sent to your configured destination after a company event is recorded. Your application receives the event details and decides how to notify a team, create a review or prepare another action.
How are webhooks different from an API?
With API retrieval, your application asks for saved records. With a webhook, CompanyDelta sends an event to your receiver when a queued delivery is processed. Many integrations use both notification and API retrieval.
Which company changes are supported?
The current event categories are ownership, directors, status, financials and details. Each requires an available source event or a configured source check. The event catalogue explains the categories and the current payload fields.
Are webhook deliveries immediate?
Not necessarily. Active paid workspaces are processed by the recurring scheduler, but source availability, successful collection, queue timing and receiver availability all affect delivery. Immediate or real-time delivery is not promised.
What happens if my endpoint is unavailable?
The delivery records a failure and a next eligible attempt. Job execution or an authorised retry can attempt it again, up to five attempts for the delivery. Inspect the receiver and delivery logs before deciding how to recover exhausted failures.
Can I receive duplicate or out-of-order events?
You should design for both. A lost acknowledgement can lead to another attempt. Deduplicate using the delivery identifier and use event identifiers when reconciling business actions. Do not assume deliveries arrive in source-date order.
How do I verify that a message came from CompanyDelta?
Use the destination's signing secret to calculate HMAC-SHA256 over the timestamp, a full stop and the exact raw body. Compare it securely with the supplied signature and apply an appropriate timestamp window. The documentation includes the header names and an example verifier.
Can I select different events for each destination?
The current queue sends new events to enabled workspace destinations without destination-specific category filters. Apply category and company filters in your receiver. Pausing a destination stops its delivery processing.
Do I need to build a receiver?
You need a compatible receiving service that verifies the signature, stores the event and handles your routing. Your team can build that service or adapt an existing workflow system. A native connector to a named CRM or messaging service is not included.
Give every relevant change a destination.
Start with the event contract and one receiving workflow.