MONITORING · EXACT EVENT CATALOGUE
Know which change produces which event.
Verified-claim monitoring
Set monitor: true on POST /v2/claims/verify. The six deterministic fields can be rechecked after an initially verified result. A detected change produces claim.stale.
Company change monitoring
The Watch Companies API lists 35 indicators, including changes to financial reports, shareholdings, appointments and contact details. This event subscription is separate from CompanyProof claim monitoring.
Read the direct API reference ↗Global Database watch indicators
These are the exact event names in the provider’s available-fields list. CompanyProof does not currently expose the provider’s watch/start, watch/stop or callback-management endpoints.
| Exact event type | Group | When it is emitted |
|---|---|---|
company.name | Company | Company name added, changed or removed |
company.status | Company | Company status changed |
company.registration_number | Company | Company registration number changed |
company.vat | Company | Company VAT code added, changed or removed |
company.address_street | Company | Company address added or changed |
company.email | Company | Company email added, changed or removed |
company.phone | Company | Company phone added, changed or removed |
company.fax | Company | Company fax added, changed or removed |
company.website | Company | Company website added, changed or removed |
company.bank | Company | Company bank account added, changed or removed |
company.employees_number | Company | Company employees number added, changed or removed |
company.trading_activity_export | Company | Company export activity added, changed or removed |
company.trading_activity_import | Company | Company import activity added, changed or removed |
company.group_structure | Company | Company group structure added, changed or removed |
company.financial | Company | Annual financial report filed |
office.identity | Locations | Office added (new entity) |
office.email | Locations | Office email added, changed or removed |
office.fax | Locations | Office fax added, changed or removed |
office.phone | Locations | Office phone added, changed or removed |
office.website | Locations | Office website added, changed or removed |
address.street | Locations | Office street address added or changed |
shareholder.holding | Shareholders | New shareholder registered (live) |
shareholder.holding_historical | Shareholders | Historical shareholding registered (backfill) |
shareholder.exit_precise | Shareholders | Shareholder exit with exact date |
shareholder.exit_approximate | Shareholders | Shareholder exit with approximate date (registry does not report the date) |
shareholder.share_type | Shareholders | Shareholder share type added |
shareholder.share_price | Shareholders | Shareholder share price added or changed |
employee.appointment | Employees | Employee joined |
employee.phone | Employees | Employee phone added, changed or removed |
employee.email | Employees | Employee email added, changed or removed |
employee.resignation_date | Employees | Employee resignation date registered |
officer.appointment | Officers | Officer appointed |
officer.phone | Officers | Officer phone added, changed or removed |
officer.email | Officers | Officer email added, changed or removed |
officer.resignation_date | Officers | Officer resignation date registered |
Read the event payload
company_data- Company identity: id, name, registration_number, country_code and date.
field- The changed indicator, for example company.email.
status- The returned change label; the webhook example uses UPDATE.
new_value / old_value- New and previous values. The example uses strings; other indicator shapes are not specified in that example.
The event-list example uses UPDATED, whereas the webhook example uses UPDATE. Preserve the distinction; the reference does not define a complete status enum.
{
"company_data": {
"id": 123,
"name": "EXAMPLE LIMITED",
"registration_number": "EXAMPLE-001",
"country_code": "GB",
"date": "2026-09-08T09:00:00Z"
},
"field": "company.email",
"status": "UPDATE",
"new_value": "new@example.com",
"old_value": "old@example.com"
}Use the provider’s available-fields list as the catalogue. Some older examples show aliases such as shareholder.name and vat_number that do not appear in that list. The watched-fields route also differs between its code sample and endpoint caption; confirm these details before a direct integration.