← Back to docs
Guides
GUIDEWebhook delivery semantics
Webhook delivery guide
This guide explains what Entylink sends to your receiver, which events are currently supported, and how retries behave so monitoring integrations can be implemented safely.
When to use it
Practical implementation contexts
Build a webhook receiver that verifies signatures against the raw request body
Handle retryable delivery failures correctly
Map supported event names into internal review or monitoring workflows
Auth
Access model
Authentication
Create and manage webhooks with an API key or dashboard session. Verify deliveries with the `secret` returned at webhook creation time.
Delivered request shape
POST /webhooks/entylink HTTP/1.1
Content-Type: application/json
User-Agent: Entylink-Webhook/1.0
X-Entylink-Event: filing.new
X-Entylink-Signature: sha256=4bc0b261...
{
"event": "filing.new",
"company_number": "08804411",
"delivered_at": "2026-04-23T12:41:33.000Z",
"data": {
"type": "CS01",
"description": "Confirmation statement with no updates"
}
}
Parameters
ParameterTypeDescription
X-Entylink-EventheaderThe event name for this delivery
X-Entylink-SignatureheaderHMAC SHA-256 signature in the form `sha256=...`
eventstringEvent name repeated in the JSON payload
company_numberstringCompany number associated with the webhook subscription
Supported events and retry behavior
Event list + delivery semanticsReference
Supported events: - officer.appointed - officer.resigned - psc.added - psc.removed - filing.new - company.status_changed Delivery behavior: - 8 total attempts - exponential backoff starting at 10 minutes - retry on HTTP 429 and any 5xx response - do not retry on other 4xx responses
Related pages
Keep moving from docs into implementation and evaluation
Next step
Move from docs into a real registry workflow.
Entylink is built for teams embedding UK company data, verification, and monitoring into products rather than manually browsing the register.