Skip to API documentation
veripoint
Login Start for free
Developer documentationAPI v2 + MCP
Request developer access
WATCH COMPANIES / WORKFLOW

Watch the changes that matter.

Subscribe to indicators, configure delivery and process the resulting company events.

  1. 01

    Read the existing callback.

    GET /companies/watch/callback inspects the current destination. Coordinate changes to this shared configuration.

  2. 02

    Configure your receiver.

    Use PUT /companies/watch/callback with an HTTPS callback URL. Confirm authentication and delivery behavior before enabling production processing.

  3. 03

    Start watching a company.

    Call POST /companies/{id}/watch/start with explicit fields. Omitting fields subscribes to all available indicators.

  4. 04

    Process changes and reconcile.

    Accept notifications at your endpoint and use the company event-history endpoint for follow-up checks. Do not assume the documented history and webhook payloads are interchangeable.

Incoming webhook · illustrative JSON
{
  "company_data": {
    "id": 12345678,
    "name": "EXAMPLE LIMITED",
    "registration_number": "01234567",
    "country_code": "GB",
    "date": "2026-09-01T12:00:00Z"
  },
  "field": "company.email",
  "status": "UPDATE",
  "new_value": "new@example.com",
  "old_value": "old@example.com"
}

Receive, validate, then process.

The provider sends POST requests to your callback. The sample payload contains company_data, field, status, new_value and old_value. Validate the payload and avoid treating its strings as trusted HTML.

As an implementation practice, process notifications idempotently and keep a reconciliation checkpoint. The reference does not specify a stable event ID, so agree a deduplication strategy with the provider rather than assuming an ID exists.

Official reference