Best APIs for Used Car Dealers: DVLA, DVSA MOT and Land Registry

Used car dealers, part-exchange platforms and vehicle buying businesses deal with the same core problem: making a fast, accurate assessment of a vehicle before agreeing to buy or value it. Three government APIs provide exactly the data needed to automate that assessment — DVLA’s Vehicle Enquiry Service for current vehicle status, DVSA’s MOT History API for full test and advisory history, and HM Land Registry for sold price data relevant to part-exchange valuations tied to property. This guide covers what each API provides, what you can build with it, and how they combine into a complete vehicle assessment workflow.

DVLA Vehicle Enquiry Service (VES) API

The DVLA Vehicle Enquiry Service API returns current registered vehicle data for any UK registration number. A single API call with a registration returns: make, model, colour, fuel type, engine capacity, year of manufacture, first registration date, CO2 emissions, Euro emission status, wheelplan, tax status, tax due date, MOT status and MOT expiry date.

This is the data that sits at the heart of any vehicle assessment or part-exchange tool. A customer enters their registration, and within a second the platform knows what the vehicle is, whether it’s taxed and when the tax expires, and when the MOT runs out. No manual lookups, no transcription errors, no reliance on the customer accurately describing their vehicle.

Access to the DVLA VES API is provided through the DVLA’s open data programme. API keys are issued via an online application — approval is typically fast. The API is free to use with generous rate limits suitable for any normal business application. Authentication uses an API key passed in the request header.

What used car dealers and part-exchange platforms build with it:

Instant vehicle identification at part-exchange. Customer enters their registration. Platform instantly returns the make, model, colour and spec without the customer having to describe the car themselves. Pre-populates the part-exchange form with accurate vehicle data. Removes the most common source of data errors in part-exchange workflows.

MOT expiry warnings. Tax and MOT expiry dates returned by the API let the platform flag vehicles with imminent MOT expiry or lapsed tax — factors that affect value. A vehicle with 2 weeks of MOT remaining is valued differently from one with 11 months remaining. Automating this flag removes the manual check.

Vehicle status verification. The tax status field confirms whether the vehicle is taxed, SORNed or untaxed. A SORN vehicle has been declared off-road — material information in any buying or valuation workflow.

The live DVLA vehicle status checker demo shows exactly what the API returns for any UK registration. The full integration service is at the DVLA API integration service.

DVSA MOT History API

Where the DVLA VES API tells you the current MOT status, the DVSA MOT History API tells you the full story. Every MOT test recorded by DVSA is available: the test date, the result (pass or fail), the mileage at test, and crucially — every advisory notice and failure item recorded by the testing station.

MOT history is one of the most revealing pieces of data available on a used vehicle. The advisory history shows recurring issues: a brake pad advisory at 40,000 miles that becomes a failure at 50,000 miles suggests the owner ignored the warning. Tyre advisories at multiple consecutive tests suggest a vehicle that has been running on marginal tyres. A consistent mileage progression confirms the odometer hasn’t been tampered with. A gap in the MOT history — where a vehicle went untested for a year or more — raises questions about its status during that period.

For used car dealers, MOT history data supports confident buying decisions. For part-exchange platforms, it provides objective third-party data that justifies the valuation offered to the customer — “we can see your vehicle has had three MOT advisories for corrosion, which affects the value we’re able to offer.” This moves the conversation from negotiation to objective fact.

DVSA MOT API access requires OAuth 2.0 authentication via Microsoft Azure AD. The application process is more involved than the DVLA API and typically takes several weeks to complete. For businesses building serious vehicle buying or dealer tools, this is worth pursuing early in the project timeline.

The live MOT history checker demo shows full test history and advisory detail for any UK registration. The integration service is at the DVSA MOT API integration service.

HM Land Registry Price Paid API

The Land Registry Price Paid API is not a vehicle data API — but it’s highly relevant to used car dealers and part-exchange businesses operating in the property-adjacent market. Several use cases connect vehicle buying to property data:

Part-exchange platforms with property context. Some vehicle buying platforms want to understand the local property market around a customer’s postcode as a proxy for understanding affordability and likelihood of completing a transaction. Property sale data by postcode provides this context.

Dealer location analysis. A dealer group evaluating new forecourt locations can use sold price data to understand the wealth profile of different catchment areas — higher property values correlate with higher average vehicle purchase values and different stock requirements.

Finance and affordability context. For dealers offering finance, recent sold prices in a customer’s postcode can inform affordability assessment alongside other data points — not as a direct underwriting tool, but as contextual data in a broader customer profile.

The Land Registry Price Paid API is freely accessible through SPARQL queries against the Land Registry linked data platform. No API key required for the price paid dataset. The live property price checker demo demonstrates postcode-level sold price data. The integration service is at the Land Registry API integration service.

Combining all three: the vehicle buying workflow

In a fully automated vehicle buying or part-exchange workflow, all three APIs contribute at different stages:

Registration lookup (DVLA VES): Customer enters registration. Platform instantly identifies the vehicle — make, model, colour, spec, tax and MOT status. Form pre-populated with accurate data. Mileage entered manually (DVLA doesn’t hold mileage; that comes from DVSA MOT history). Time: 1–2 seconds.

MOT history check (DVSA): Full test history retrieved. Mileage at each test cross-checked against declared mileage for consistency. Advisories and failures reviewed automatically. High-risk flags raised: excessive advisories, structural failure history, mileage inconsistency, SORN history. Time: 2–3 seconds.

Valuation adjustment: The platform applies valuation rules to the data. A clean MOT history with no advisories supports a strong offer. Multiple recurring advisories, a failure history or a mileage inconsistency justifies a lower offer or a hold-for-inspection flag. The valuation is data-driven and auditable, not subjective.

Automated payout (Revolut API): When the vehicle is received, inspected and the offer confirmed, the payout triggers automatically — customer’s bank details verified against the account holder name, OTP verification, payment released. See the Revolut Business API integration service for the payment automation side.

For the DVLA integration, see the DVLA API integration service. For DVSA MOT, see the DVSA MOT API integration service. For Land Registry, see the Land Registry API integration service.

Related posts

• DVLA API integration guide
• DVSA MOT API integration guide
• Land Registry API integration guide
• Automating payments with the Revolut API

If you need help with a custom API integration for your website or business application, I can help. I build bespoke API integrations for UK businesses. See API integration pricing or get in touch to discuss your project.