
Plate, VIN, and chassis in JSON: preserving identifiers
Why these values should travel as strings, which normalisations are safe, and how to prevent cleanup from merging different vehicles.
Read articleMobility · API V1
Find active safety campaigns by make and VIN or chassis number.
Controlled, account-enabled access
WHAT IT SOLVES
Find active safety campaigns by make and VIN or chassis number. This public page presents the use case and a safe preview; operational configuration is managed inside the portal.
REQUEST DATA
The public page for this version uses Vehicles.
itemsVehiclesINTEGRATION FLOW
Start with your use case and the minimum required data.
We configure scope, credentials, and capacity for your account.
Consume JSON inside your product or operating workflow.
LOCAL SANDBOX
Edit the example and generate a JSON preview in your browser. Live requests require an enabled account.
GUIDES AND ANALYSIS

Why these values should travel as strings, which normalisations are safe, and how to prevent cleanup from merging different vehicles.
Read article
Build an operational vehicle view without confusing signals from different sources, dates, and purposes.
Read articleFREQUENTLY ASKED QUESTIONS
Find active safety campaigns by make and VIN or chassis number.
The public v1 contract accepts items. This page identifies which fields are required or optional.
Up to 8,000 items per request.
Yes. The sandbox creates a local preview with synthetic data; it does not run a live request or send information.
Access is controlled and enabled per account. Requests and operational configuration are managed through the API.ar portal.
NEXT STEP
Open the portal to request access and continue with a secure integration.
Open the portal