DVLA API Integration: What Can It Do for Your Business?

DVLA API integration is the process of connecting your software directly to official UK government vehicle data. The core service, the DVLA Vehicle Enquiry Service API, is free to use and returns tax status, MOT status, make, colour, fuel type and CO2 emissions for any registered vehicle from a single registration number lookup, typically in under a second.

The Driver and Vehicle Licensing Agency holds records for more than 41 million licensed vehicles in the United Kingdom (Department for Transport vehicle licensing statistics, 2024). Its APIs, together with the DVSA’s MOT History API, put that data within reach of any organisation that registers for access: fleet operators, insurers, dealerships, leasing firms and software teams building automotive products.

Happy Company is an engineering studio that builds AI agents and custom software for business leaders and CTOs across the UK and Europe. We run DVLA and DVSA integrations in production, including inside CarFile, our vehicle compliance product, so this guide reflects what actually happens when you build against these APIs, not just what the documentation says.

What is DVLA API integration and what data can you access?

DVLA API integration means connecting an application to the Driver and Vehicle Licensing Agency’s data services so it can query official records programmatically. The main service, the Vehicle Enquiry Service (VES) API, accepts a registration number and returns tax status, tax due date, MOT status, MOT expiry date, make, colour, fuel type, engine capacity, CO2 emissions and date of first registration.

The VES API is a REST service that returns JSON, which makes it straightforward to consume from any modern stack. You send a POST request containing a registration number and receive a structured vehicle record in response. There is no scraping, no screen automation and no third-party reseller in the chain: the data comes from the same records the DVLA itself uses.

Two boundaries matter from day one. First, the VES API covers vehicles, not drivers; licence checking is a separate, contracted service. Second, it returns the current MOT status but not the test history. Full MOT records, including mileage readings, defects and advisories, come from the Driver and Vehicle Standards Agency (DVSA) through a separate API. Most production systems integrate both.

Which DVLA and DVSA APIs are available in 2026?

Four services cover most business needs in 2026: the DVLA Vehicle Enquiry Service API for tax and vehicle details, the DVSA MOT History API for test results and mileage, DVLA Access to Driver Data for licence checking, and the DVLA KADOE service for registered keeper details. The first two are free; the driver and keeper services require commercial agreements.

Service	Agency	What it returns	Access model	Cost
Vehicle Enquiry Service (VES) API	DVLA	Tax status, MOT status, make, colour, fuel type, CO2, engine size	Self-service registration, API key	Free
MOT History API	DVSA	Full MOT test history, mileage readings, defects, advisories	Registration, API key plus OAuth 2.0 client credentials	Free
Access to Driver Data (ADD)	DVLA	Licence status, entitlements, penalty points, disqualifications	Commercial contract and approval	Charged per enquiry
KADOE	DVLA	Registered keeper name and address	Contract, requires reasonable cause	Charged per request

What is the difference between the DVLA and the DVSA?

The DVLA registers drivers and vehicles and collects vehicle tax; the DVSA administers MOT and driving tests. This split explains why vehicle tax data and MOT history live behind different APIs with different registration processes. You register for the VES API on the DVLA developer portal and for MOT data through the DVSA MOT History API documentation.

How much does DVLA API integration cost?

The DVLA Vehicle Enquiry Service API and the DVSA MOT History API are both free to use, so most vehicle-data integrations carry no licensing cost at all. Access to Driver Data and KADOE keeper enquiries are charged per lookup under commercial contracts with the DVLA. The real cost is engineering time: expect two to six weeks for a production-grade build.

Free does not mean unlimited. Both free APIs enforce rate limits per API key, and the DVLA can suspend keys that breach them. A well-built integration caches responses, batches its refresh cycles and backs off on 429 responses, which keeps a fleet of thousands of vehicles comfortably within quota.

On engineering effort, a minimal lookup feature is a few days of work. A production system, with input validation, retries, caching, monitoring, secret management and reconciliation of the two data sources, typically lands between two and six weeks depending on how deeply the data feeds your workflows. If DVLA data drives real decisions in your business, budget for the reliability work, not just the happy path.

How do you integrate the DVLA Vehicle Enquiry Service API?

You register on the DVLA developer portal, receive an API key, and send an HTTPS POST request to the vehicle enquiry endpoint with the registration number in a JSON body. The API responds with the full vehicle record. A robust integration, including validation, error handling and caching, is usually one to two sprints of work for an experienced team.

The practical steps:

Register for access. Sign up on the DVLA developer portal and request a VES API key. Approval for the test and production environments is straightforward for legitimate business use.
Store the key securely. Treat the API key as a secret: keep it in a vault or environment configuration, never in source control, and rotate it on a schedule.
Normalise input before you query. Strip spaces, uppercase the plate and validate the format. ANPR feeds and manual entry both produce plates with confusable characters, such as the letter O for zero and the letter I for one.
Call the endpoint. POST the registration number to the vehicle enquiry endpoint with the key in the request header. A healthy response returns in well under a second.
Handle every response class. A 200 gives you the record; a 404 means the plate is not found, which is common for personalised or recently transferred registrations; a 400 is a malformed request; a 429 means you have hit the rate limit and should back off.
Cache and monitor. Vehicle attributes such as make and colour never change, and tax or MOT status rarely changes more than once a day, so cache aggressively and refresh on a schedule rather than per page view.

How does authentication work for the DVSA MOT History API?

The MOT History API uses OAuth 2.0 client credentials on top of an API key. Your service exchanges a client ID and secret for a bearer token, attaches both the token and the API key to each request, and refreshes the token before it expires, roughly every hour. Build token caching in from the start; requesting a fresh token per call is a common cause of throttling.

How do AI agents use DVLA data in production?

AI agents treat DVLA and DVSA APIs as tools they call autonomously. An agent monitoring a fleet can check tax and MOT status on a schedule, spot expiry dates approaching, flag mileage anomalies in MOT history, and open renewal tasks or notify the right person, all without anyone triggering a lookup manually. Happy Company runs this pattern in production.

Our clearest example is CarFile, our vehicle compliance product. CarFile sweeps every tracked vehicle against the VES and MOT History APIs, detects changes since the previous run, and turns them into actions: a tax due date within 14 days becomes a reminder, a failed MOT becomes an alert with the defect list attached, and an odometer reading lower than the previous test becomes a flag worth investigating. We wrote about the reminder side of this in Never miss an MOT, tax or insurance date again.

The same architecture scales to commercial fleets. Instead of an administrator checking vehicles on GOV.UK one plate at a time, an agent reconciles the whole fleet nightly and surfaces only the exceptions. For a 500-vehicle fleet that replaces hours of weekly manual checking with a report that takes minutes to review. Our guide to fleet management software development covers where this fits in a broader build.

The engineering lesson from running these agents is that the API integration is the easy half. The value comes from the layer above it: the change detection, the prioritisation of what a human should actually see, and the audit trail of what the agent did and why.

What are the common pitfalls with DVLA API integration?

The most common failures are unhandled 404 responses for personalised or recently transferred plates, tight query loops that breach rate limits, stale caches treated as live data, and assuming the Vehicle Enquiry Service returns MOT history when it only returns current MOT status. All four are avoidable with validation, backoff logic and honest cache expiry.

Data lag is real. After a keeper taxes a vehicle, the change can take up to five working days to appear in the enquiry data. Build your alerts to tolerate this window, or you will send false “untaxed” warnings about compliant vehicles.
Not every plate resolves. New registrations, imports and plates mid-transfer return 404. Treat “not found” as a state to display, not an error to retry forever.
The VES API has no VIN or keeper data. If your process needs to confirm identity or ownership, VES alone cannot do it; keeper data requires KADOE and a lawful basis for the request.
Driver data is personal data. Licence checks through Access to Driver Data fall under UK GDPR. You need driver consent or another lawful basis, retention rules and access controls before the first API call.
Plan for outages. Government APIs have maintenance windows. Queue lookups and degrade gracefully rather than failing user journeys when the upstream is unavailable.

Frequently Asked Questions

Is the DVLA API free to use?

Yes. The DVLA Vehicle Enquiry Service API is free, and so is the DVSA MOT History API. Both require registration and enforce rate limits per API key. Only the contracted services carry fees: DVLA Access to Driver Data for licence checking and the KADOE service for registered keeper details are charged per enquiry under commercial agreements with the DVLA.

What data does the DVLA Vehicle Enquiry Service API return?

For a given registration number it returns tax status, tax due date, MOT status, MOT expiry date, make, colour, fuel type, engine capacity, CO2 emissions, year of manufacture and date of first registration. It does not return the VIN, the registered keeper’s details, insurance status or the vehicle’s MOT test history, which comes from the separate DVSA MOT History API.

Can I check someone’s driving licence through a DVLA API?

Yes, but not through the free services. DVLA Access to Driver Data provides licence status, entitlements, penalty points and disqualifications through an API. It requires a commercial contract with the DVLA, per-enquiry fees and a lawful basis under UK GDPR, usually the driver’s consent. It is used mainly by insurers, fleet operators and employers running driver risk checks.

How do I get MOT history for a vehicle by API?

Register for the DVSA MOT History API through its official documentation portal. Access is free for legitimate business use. Authentication combines an API key with OAuth 2.0 client credentials, and the API returns every recorded MOT test for a vehicle, including dates, results, odometer readings, failure defects and advisories, which makes it valuable for valuations, fraud checks and fleet compliance.

How quickly does DVLA data update after taxing a vehicle or an MOT test?

MOT results usually appear soon after the testing station records them, often the same day. Vehicle tax status can take up to five working days to update in the enquiry data after a keeper taxes a vehicle. Any system that alerts on untaxed vehicles should allow for this lag to avoid warning about vehicles that are actually compliant.

Do I need approval to use the DVLA Vehicle Enquiry Service API?

Yes, but the process is light. You register on the DVLA developer portal, describe your use case and receive API keys for the test environment, then request production access. There is no fee and no commercial contract for the Vehicle Enquiry Service. Approval for driver data and keeper data services is a separate, stricter process involving contracts and compliance checks.

Where should you start with DVLA API integration?

Start with the free Vehicle Enquiry Service API: register on the DVLA developer portal, prove the lookup in your test environment within a day, then invest in the production layer of caching, error handling and monitoring. Add the DVSA MOT History API when you need test records, and the contracted services only when your use case genuinely demands driver or keeper data.

If you would rather ship the outcome than the plumbing, that is what we do. Happy Company builds DVLA and DVSA integrations, and the AI agents that act on the data, for fleets, dealerships and automotive platforms across the UK and Europe. Talk to Happy Company about your DVLA API integration, and we will show you what we already run in production.