Fleet operator · London business
ulez_compliant: true or false. Derived from DVLA data.
The ULEZ daily charge is £12.50 per non-compliant vehicle, every day it enters the zone. For a fleet with multiple London-operating diesels, that accumulates quickly — and most operators don't have a programmatic way to identify which specific vehicles are generating the exposure. Zyfy derives ULEZ compliance from the official DVLA euro emission standard and returns it as a single boolean per VRM.
Relevant signals
These fields are returned on every response and are ready to wire into your application logic.
| Signal | Relevance | What it tells you |
|---|---|---|
| signals.ulezCompliant | Critical | Boolean. Derived from euroEmissionStandard and fuelType against TfL ULEZ thresholds. Petrol must be Euro 4 or newer; diesel must be Euro 6. Electric is always compliant. |
| signals.euroEmissionStandard | Critical | Euro 1–6, electric, or null from DVLA. The underlying data point from which ulezCompliant is derived. Useful for understanding exactly why a vehicle fails. |
| fuelType | High | Petrol, diesel, electric, or hybrid_electric. Diesel vehicles face a stricter ULEZ threshold (Euro 6) than petrol (Euro 4). Electric and hydrogen vehicles are always compliant. |
| signals.co2EmissionsGPerKm | Medium | CO₂ output in grams per kilometre from DVLA. High values confirm a high-emission vehicle — useful context alongside the ULEZ compliance flag. |
Live example
A real-world request and the response it returns.
Request
curl https://zyfy.uk/v1/vehicle/AB12CDE \
-H "X-API-Key: your_api_key"Response
{
"registration": "AB12CDE",
"make": "MERCEDES-BENZ",
"model": "SPRINTER",
"colour": "WHITE",
"fuelType": "diesel",
"engineCapacityCc": 2143,
"yearOfManufacture": 2017,
"vehicleAgeYears": 8,
"monthOfFirstRegistration": "2017-11",
"summary": {
"vehicleRiskLevel": "low",
"motRiskLevel": "low"
},
"signals": {
"co2EmissionsGPerKm": 198,
"euroEmissionStandard": "EURO 5",
"ulezCompliant": false,
"taxStatus": "taxed",
"taxDueDate": "2026-12-01",
"motStatus": "valid",
"motExpiryDate": "2026-11-14",
"odometerTrend": "consistent"
},
"enrichmentPending": false
}Example data is illustrative only. Responses shown include a subset of signals for clarity — the full response contains additional fields. See the signal reference for the complete list.
What you get
- ✓ Identify non-compliant fleet vehicles in one sweep — Loop your fleet registrations through the API. Every vehicle returning ulez_compliant: false is generating a daily charge for any London zone entry. Quantify the exposure before planning replacements.
- ✓ One boolean, no emission tables to maintain — TfL's compliance thresholds differ by fuel type and are not trivially derived from a V5C. Zyfy derives ulez_compliant server-side from DVLA data — you get the boolean, not the calculation.
- ✓ Filter and route by compliance at dispatch — Integrate into your dispatch or routing system. Assign London deliveries to ulez_compliant: true vehicles automatically. Avoid accidental charges on jobs where a compliant vehicle is available.
- ✓ Check before purchasing fleet additions — Query a VRM before buying a used vehicle for fleet use. A non-compliant diesel at a competitive price carries a hidden ongoing cost for London operations. Know before you commit.
Find out which fleet vehicles are generating ULEZ charges.
Free tier includes 100 requests per month. No credit card, no sales call.