Monitor approved UK businesses with webhooks instead of polling
Use Entylink webhooks to turn approved UK businesses into monitored entities, so filings, officer changes, PSC changes, and status changes flow into operational systems without polling.
Start from the real implementation problem
Keep the setup explicit
An approved company number you want to monitor
A public HTTPS endpoint that can receive webhook deliveries
A stored signing secret for webhook verification
Decide which events actually matter operationally
Entylink supports event names such as `filing.new`, `officer.appointed`, `officer.resigned`, `psc.added`, `psc.removed`, and `company.status_changed`. Subscribe only to the ones that should trigger review.
Create the webhook after approval
Do not create monitoring before you know the final company number you care about. Monitoring belongs to the approved entity set.
curl https://api.entylink.com/v1/webhooks \
-X POST \
-H "Authorization: Bearer $ENTYLINK_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/webhooks/entylink",
"company_number": "08804411",
"events": ["filing.new", "company.status_changed", "psc.added"]
}'Push deliveries into a queue, not directly into business logic
A monitoring event should usually enter a queue or review pipeline first. That keeps your webhook endpoint fast, reliable, and easier to retry safely.
Attach monitoring to the same entity model used at onboarding
Keep one canonical company number in your own system. Use that same key to join the initial verification case and later monitoring events.