Solutions · Insurance
Price policies on the right vehicle data
The customer types their plate, and your calculator gets kind, usage, weight, power and model year straight from the register's extract. The data holds no personal data.
Fields you typically use
- Kind and primary usage
- Power and displacement
- Total weight and own weight
- Model year and first registration
- Make, model and variant
- Registration status
Vehicle data for insurance pricing
-
Fewer wrong answers
The customer doesn't pick model and power. You get them from the register.
-
A short quote flow
One plate instead of a long form means fewer people drop off.
-
No personal data
The API has the vehicle, not the owner. That keeps data processing simpler.
What a call looks like
Every response is JSON with stable field names. IDs are strings, dates are YYYY-MM-DD.
Quickstartcurl -H "X-Api-Key: $MOTORBAY_API_KEY" \
"https://api.motorbay.app/v1/vehicles/plate/AB12345" {
"id": "4815162342",
"registrationNumber": "AB12345",
"vin": "YV1AB12C3D4567890",
"status": "registered",
"registrationStatus": "registered",
"firstRegisteredOn": "2019-03-14",
"kind": {
"id": "1",
"name": "Personbil",
"originalName": "Personbil"
},
"make": {
"id": "42",
"name": "VOLVO",
"originalName": "VOLVO"
},
"model": {
"id": "1234",
"name": "V60",
"originalName": "V60"
},
"color": {
"id": "7",
"name": "Grå",
"originalName": "Grå"
},
"emissionStandard": {
"id": "9",
"name": "Euro 6",
"originalName": "Euro 6"
}
} Make your first lookup today
Create an account, make an API key and send your first call. The quickstart takes about five minutes. Your first 1,000 requests every month are free, and you need no card.