DVLA vehicle lookup explained: what data you get, and how to use it

The DVLA's free vehicle lookup is one of the best things to happen to UK garage software in the last decade. Type a registration, get make, model, colour, fuel type, engine size, year, MOT status, and tax status. No data entry, no asking the customer to read out the VIN, no manually checking with the V5C.

Most workshop owners I talk to either do not know this exists, or use a paid service that wraps the same free API and charges them per lookup. This post explains what you actually get, what you do not, and how to combine it with the MOT history API for a complete view of every car that comes through the door.

What DVLA's free Vehicle Enquiry Service returns

The DVLA's Vehicle Enquiry API is free, public, and returns per registration:

• Make (Ford, BMW, Audi, etc.)
• Colour (current registered colour)
• Fuel type (petrol, diesel, hybrid, electric)
• Engine capacity (in cc)
• Year of manufacture
• Date first registered in the UK
• CO2 emissions (if recorded)
• MOT status (valid, expired, or not required)
• MOT expiry date (if currently valid)
• Tax status (taxed, untaxed, SORN)
• Tax due date (if currently taxed)
• Type approval (M1, N1, etc.)
• Wheelplan (2-axle rigid body, etc.)

Notably absent: model. You get "Ford" but not "Focus". For model you need a separate lookup or you ask the customer.

The API rate limit is 15 requests per second per IP, which is more than enough for a workshop. You sign up for an API key on the DVLA developer portal, it is free, no card required.

What it does not give you

Three big gaps, all important:

No VIN. The Vehicle Identification Number is what you need for parts ordering. DVLA does not share it through the API. You read it off the V5C, the dashboard plate, or the door pillar.

No service history. DVLA tracks ownership and tax, not service. If you want to know whether the car was serviced at a main dealer or what work has been done, the customer has to tell you.

No mileage (current). DVLA records mileage at MOT (which comes through the DVSA MOT history API, not DVLA), but does not give you a real-time current mileage. You read it off the odometer when the car comes in.

Why this matters for a UK garage

Three concrete uses, ordered by daily impact:

1. Data entry savings. Every job in a workshop starts with a vehicle. Without DVLA lookup, the receptionist asks the customer to read out make, model, colour, year, and writes it down. With DVLA lookup, you type the registration, the form auto-fills, and the receptionist confirms the year and colour with the customer in 10 seconds. Saved time per job: 90 seconds to 2 minutes. Over a busy week that is hours.

2. Wrong-parts prevention. Customer says "it's a 2018 Focus 1.0 EcoBoost". Receptionist enters that, parts manager orders parts for a 2018 1.0 EcoBoost. Car arrives, it is actually a 2017 1.5 TDCi diesel. Parts are wrong, day is wasted. DVLA lookup catches the year and engine capacity discrepancy before parts get ordered.

3. Customer claim validation. Customer brings car in claiming it failed MOT yesterday and the previous garage was unfair. You look up the reg: MOT status is "valid" with eight months remaining. Either the customer is confused or there is something else going on. Either way you have facts before you start work.

Combining DVLA with DVSA MOT history

DVLA gives you current MOT status. The DVSA MOT history API gives you every test the vehicle has ever had: pass, fail, advisories, mileage at each test, fail reasons.

Together they answer the questions a customer cannot reliably answer themselves:

• When was the last MOT? (DVSA)
• What advisories came up? (DVSA)
• Has it ever failed for the same issue twice? (DVSA)
• What is the mileage history? (DVSA, recorded at each MOT)
• Is the car currently taxed? (DVLA)
• When does road tax expire? (DVLA)
• Is the registered colour correct? (DVLA, useful if a respray happened)

For a workshop, the most valuable combination is: registered fuel type (DVLA) plus MOT advisory history (DVSA). A car that has been flagged twice for the same advisory at the previous two MOTs is a car where the customer has been ignoring the workshop's recommendations. That is useful context before you give a quote.

The limitations of DVSA MOT data

Two caveats most owners do not realise:

1. Mileage at MOT can be lower than current mileage by months. An MOT in February with 87,500 miles tells you the mileage in February, not today. A car driven 1,500 miles a month is on 95,000 by October. Do not quote based on MOT mileage.

2. Advisory wording is the tester's free text. Two different testers describing the same brake disc issue may use different words. Searching MOT advisories programmatically is hit-and-miss.

These are not deal-breakers, just things to remember when you rely on the data.

How to build it yourself

Both APIs are well-documented and free. The build pattern:

1. Sign up for DVLA API key (Vehicle Enquiry Service).
2. Sign up for DVSA API key (MOT history).
3. Build a form: customer types registration, you call both APIs in parallel, you display the merged result.
4. Cache the response for 24 hours so you do not re-query the same reg if the customer is back in twice.

For a technically confident workshop, this is half a day of work. The harder part is fitting it into an existing job-creation flow rather than running it as a standalone tool.

How Autera does this

Every time you create a job in Autera (web or mobile app), typing the registration triggers both lookups automatically:

• DVLA fills make, colour, fuel type, engine size, year, MOT and tax status
• DVSA returns the full MOT test history, displayed inline on the job

You confirm with the customer, hit Save, and the vehicle is on the system with no manual typing. The next time the same car comes in (same registration, different year), Autera pulls the existing record and you do not even need the lookup again.

The whole flow takes about 8 seconds. Same time as it would take a receptionist to write down "Ford Focus, blue, 2018" with a pen.

Privacy note

The DVLA API and DVSA API both return data about specific vehicles. They do not return the owner's name or address. You are looking up the car, not the person. This sits well within UK GDPR for the purpose of providing a workshop service to that car.

What you should not do is store the lookup data and use it for purposes unrelated to the service relationship (selling it to insurance companies, building a database of cars to spam with marketing, etc.). DVLA's API terms cover this and you can lose access if you breach them.

When the API is not enough

For maybe 1 in 50 vehicles, the DVLA lookup returns "vehicle not found" or partial data. Usually this is:

• A car newly registered in the last 24 hours (data not yet propagated)
• A car that has just changed plates (cherished transfer)
• A foreign-registered vehicle with a UK MOT (rare)
• A motorcycle (different system)

For these, you fall back to manually entering the data from the V5C. Annoying but rare.

Worth saying clearly

This is a free public service paid for with your tax. Use it. There is no excuse for a UK workshop in 2026 to be manually typing make, model, and year for every job. Either build the API into your tool, or pick a workshop tool that already has it.

Autera handles all of this automatically. Every job. Every time. Try free for 14 days → or book a demo.