Entylink
Company monitoring API

Monitor UK company changes with webhooks instead of polling the registry yourself

Use Entylink to monitor UK company filings, officer changes, PSC updates, and other registry events through webhooks built for compliance, fraud, credit, and onboarding workflows.

company monitoring apicompany alerts apicompanies house webhookscompany change alerts api
Key metrics
Delivery
Webhook-first
Operational change events
Event types
Filings, officers, PSCs
Monitor specific entity changes
Fit
Risk workflows
Useful after onboarding too
Who this is for

Built for engineering and operational teams

Platform and backend engineers replacing manual polling jobsRisk, fraud, compliance, and credit teams monitoring approved portfoliosFintech onboarding teams that need ongoing business monitoring after approval
Trigger reviews when a company files, appoints a director, or changes PSCs
Keep internal systems current without building raw registry stream infrastructure
Subscribe monitored entities and deliver changes into Slack, queues, or internal services
What you get

What the API gives you

01

Webhook delivery for six registry event types

Subscribe any company to `filing.new`, `officer.appointed`, `officer.resigned`, `psc.added`, `psc.removed`, or `company.status_changed`. Entylink polls the registry and delivers signed payloads to your HTTPS endpoint.

02

Events that matter to risk and compliance workflows

Fraud, compliance, credit, and onboarding teams care about what changed after the initial review: new filings, director appointments, ownership changes, and status updates — all delivered as structured JSON.

03

No stream infrastructure to own

Building on the raw Companies House stream means managing long-lived connections, reconnect backoff, and delivery guarantees yourself. Entylink handles that layer and delivers clean events to your endpoint.

Implementation

A working example in minutes

Real endpoints, real request shapes — copy into your project and be live in minutes.

Webhook flowPOST /v1/webhooks
API example
curl https://api.entylink.com/v1/webhooks \
  -X POST \
  -H "Authorization: Bearer $ENTYLINK_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "company_number": "08804411",
    "events": ["filing.new", "officer.appointed", "psc.added"],
    "url": "https://example.com/webhooks/company-monitoring"
  }'
Monitoring is commercially valuable because it keeps the registry data useful after the first lookup.
Why teams switch

Why teams choose Entylink

01

Polling the registry is inefficient and brittle in production.

02

Owning stream ingestion is infrastructure work most product teams do not want.

03

Ongoing monitoring is one of the clearest upgrade paths from lookup APIs to higher-value workflows.

FAQ

Frequently asked questions

What webhook events does Entylink support?

Entylink delivers `filing.new`, `officer.appointed`, `officer.resigned`, `psc.added`, `psc.removed`, and `company.status_changed`. Each payload is signed with HMAC-SHA256 using the webhook secret returned when you create the subscription.

What kind of teams buy this?

Compliance, fraud, credit, and onboarding teams are the natural buyers because ongoing entity change detection is operationally important to them.

Is this just for fintechs?

No. Fintech is a strong fit, but supplier due diligence, credit, and other risk workflows can also justify ongoing monitoring.

Get started

UK business verification.
Without the build time.

Self-serve access. Public pricing. Make your first API call in minutes.