Connect
On this page we explain per system (software often used on the islands as single source of truth), per island and our API how everything can be integrated: whether we receive data from your system or we can send data to you.
Our API: receive and send
CVR acts as the central register. Integration is via the REST API v1. Depending on your role you can send data to us (we receive) or request data from us (we send).
What we receive
Partners send us among other things: insurance status (insurance/status), inspection results (inspection/status), evidence documents (upload), payment confirmations, mutations (registration, ownership, plate). Authentication via Bearer token; recommended: Idempotency-Key for mutations.
What we send
Partners can request from us among other things: plate lookup, vehicle and registration status, insurance, vehicle inspection (APK), tax status, enforcement information. For enforcement and municipality a purposeCode is required; for police also caseRef.
Per system type: receive or send
Below per type of software/actor whether CVR receives data from that system or sends data to that system (or both).
Insurer
Insurance status, policy data, evidence documents.
Ontvangen: We receive: status notifications (active/inactive/pending), policy + VIN, evidence uploads, approvals/rejections.
Zenden: We send: (optional) confirmation and status after processing. Plate lookup via enforcement/municipality API if authorised.
Tax authority
Road tax, assessments, payments.
Ontvangen: We receive: (if linked) payment or waiver confirmation.
Zenden: We send: assessments per person/year, payment status; events on start/end of tax liability (on registration/transfer).
Municipality / Registration
Plate, vehicle, owner, activation.
Ontvangen: We receive: vehicle creation, ownership/holder, activation/suspension, plate issue, transfers.
Zenden: We send: plate lookup (with purposeCode), vehicle and registration status, insurance, inspection (APK) and tax for decision-making.
Police / Enforcement
Lookup, blocks, actions.
Ontvangen: We receive: enforcement actions (block/impound) and caseRef for audit.
Zenden: We send: full plate lookup (registration, insurance, inspection/APK, tax, blocks) via POST /enforcement/check; status and actions per plate.
Inspection station
Vehicle inspection (APK); inspection results per registration.
Ontvangen: We receive: inspection result via POST /inspection/status (registration_id, inspected_at, valid_until, optional source).
Zenden: We send: plate lookup includes inspection status (is_valid, valid_until); partners with enforcement rights can request this.
Per island: systems and integration
Each island may use different packages or local systems as single source of truth. Below an overview per island and how integration with CVR works.
Bonaire
Often: local administration (Excel, documents), Tax Authority CN (road tax), insurers (policy).
CVR receives from: municipality/registration (vehicle, plate, activation), insurers (status), possibly tax (payment). CVR sends to: police (lookup), municipality (status for decision), tax (events). One digital register as source for all parties.
Curaçao
Often: national ordinances, own registration, Landsontvanger (tax), insurers.
CVR receives: registration decisions, ownership, insurance status. CVR sends: lookup for police and municipality, tax events to Landsontvanger, status for transfer and enforcement.
Sint Maarten
Often: local government administration, insurers, enforcement.
CVR receives: vehicle and insurance data (e.g. via cc-mail or API). CVR sends: real-time status for enforcement and municipality; insurers do not need a separate link if they report via our platform.
Saba
Small scale: limited local systems, central workflows desired.
CVR receives: registration and insurance status (few local actions). CVR sends: dashboard and status for island administration; less own IT needed.
Sint Eustatius
BES context: simplicity and transparency, uniform rules.
CVR receives: mutations as on other BES islands. CVR sends: policy information and status for government and oversight.
How to connect
Connect your system via the REST API v1. See the API documentation and the Partner Integration Guide for endpoints, authentication and governance.
- API documentation — OpenAPI/Swagger en endpoints
docs/PARTNER_INTEGRATION_GUIDE.md— Partner Integration Guide (authenticatie, headers, governance)