If you are building anything that touches a UK vehicle — a dealer CRM, an insurance quote journey, a fleet compliance tool, an ANPR pipeline — you eventually need the same thing: reliable, official vehicle data from nothing more than a number plate. This guide explains what a UK vehicle data API actually gives you, how the data sources fit together, and how to choose a provider that won't lock you into a contract or bill you for lookups that fail.
What a "UK vehicle data API" actually returns
"Vehicle data" is an umbrella term. In practice it breaks down into a handful of distinct datasets, each with its own official source:
- Registration details — make, model, colour, fuel type, engine size, year of manufacture, CO₂ emissions, tax status and MOT status. Sourced from the DVLA Vehicle Enquiry Service.
- MOT history — every DVSA test, pass/fail result, recorded mileage and advisory notes, going back years. Sourced from the DVSA MOT history dataset.
- Valuation — trade, retail and private values for the specific vehicle.
- Provenance — outstanding finance, insurance write-off category, stolen markers and mileage anomalies (the checks people mean when they say "HPI check").
- Specification & options — the factory equipment actually fitted to that VIN.
- Tyre, battery/EV and imagery data for more specialist use cases.
A good API exposes all of these through one gateway and returns them in a single, consistent JSON schema, so you integrate once instead of learning five different providers' response formats.
At VehicleMatic, every one of these is a first-party product you call by registration (VRM). Browse the full list on the API catalog, or try live-shaped responses without an account in the sandbox.
The single-gateway, normalized-JSON model
The biggest hidden cost in vehicle data isn't the per-lookup price — it's integration and maintenance. If you stitch together the raw DVLA VES API, the DVSA MOT API and a separate valuation provider, you're maintaining three auth mechanisms, three error formats and three data shapes.
VehicleMatic normalizes all of it. You authenticate once with an API key, call /products/{product}/api/live/{operation} with a registration, and get back the same predictable envelope every time. Add a new dataset later and it's the same pattern — no new SDK, no new parsing.
POST /products/vehicle-details/api/live/lookup
X-API-KEY: your_key_here
{ "registration": "AB12CDE" }
Because the response schema is stable across products, you can build one internal "vehicle" model and populate it from whichever lookups your use case needs.
Pay-per-lookup vs contracts
Legacy providers in this space often want an annual contract, a minimum monthly spend, or a per-seat licence. That's a poor fit if your volume is spiky (seasonal dealers), just starting (a new app), or genuinely enormous (ANPR at scale).
VehicleMatic is pay-per-lookup on credits:
- 10 free lookups when you sign up, so you can integrate and test before paying anything.
- Pay-as-you-go top-ups — buy credit when you need it; the larger the top-up, the better your per-lookup rate.
- Monthly plans for predictable volume, with over-usage billed in arrears rather than blocked.
- No contracts, no lock-in — stop any time; unused credit stays valid.
Crucially, you're only charged on a successful lookup. If the upstream register has no record, or the call fails, you don't pay for it — you never get billed for fabricated or empty data. See the current tiers on the pricing page, or model your spend with the API cost calculator.
Indicative best-tier rates give a sense of scale: MOT history from around 2p per lookup, core vehicle details from around 4p, and full provenance checks from around £2.34 — the exact rate depends on the plan tier you're on.
How to choose a UK vehicle data API
When you're comparing providers, weigh these five things:
- Coverage — does it return the specific fields you need, or just a subset? Check MOT advisories, write-off categories (A/B/S/N), CO₂ and factory spec explicitly.
- Official sourcing — is the data from DVLA/DVSA and licensed partners, or scraped? VehicleMatic sources every field from an official register or licensed data partner (see data & coverage).
- Billing model — pay-per-lookup vs contract; charged-on-success vs charged-on-attempt.
- Integration effort — one normalized schema vs several bespoke ones; is there a sandbox and an interactive API explorer?
- Latency & reliability — matters enormously for real-time flows like ANPR and quote journeys.
Getting started
- Create an account — you get 10 free lookups immediately.
- Explore the sandbox and each product's API explorer to see the exact response shape.
- Generate an API key in the customer portal and make your first live call.
- Top up credit or pick a monthly plan when you're ready to go to production.
Frequently asked questions
Do I need one API key per dataset? No. One key works across every product; you choose which lookups to call per request.
What happens if a lookup returns no data? You aren't charged. Billing is on successful delivery only.
Is the data UK-only? Yes. VehicleMatic covers Great Britain and Northern Ireland via DVLA, DVSA and licensed partners.
Can I try it before paying? Yes — the sandbox needs no account, and sign-up includes 10 free live lookups.
Ready to build? Start with the API catalog or jump straight to pricing.