Overview

The MOT history API gives authorised third-party organisations a way to access MOT test history information for vehicles.

The information includes:

• MOT test date
• MOT expiry date
• test result
• mileage reading
• MOT test number
• reasons for failure and advisory notices
• first MOT due date for new vehicles
• vehicle ID
• vehicle registration date
• vehicle manufacturing date
• cylinder capacity of the engine

API endpoints

You can use the API from 4 different endpoints:

1. MOT test history for a single vehicle using a registration number

   Search for the MOT history using just the registration number of the vehicle. Use this method if you want the MOT history for a limited number of vehicles or want to check the latest information for a vehicle.

2. MOT test history for all vehicles

   Use this method if you are interested in a large number of vehicles and want to keep an offline copy.

3. MOT test history for all vehicles tested on a certain date

   Use this method to find out which vehicles have been tested on a particular date. You can also use this method to maintain the data that you have extracted using either of the other two methods above.

4. MOT test history using a vehicle's unique identifier

   Search for the MOT history using the vehicle's unique identifier. Use this method if you want the MOT history of a vehicle that has changed its registration number.

Amount of use

Depending on how much data you want to access, we recommend the following ways of using the API.

1. Fewer than 150,000 requests a day

   Use endpoint 1 to get MOT test history data for individual vehicles when necessary.

2. More than 150,000 requests a day and interested in up to 10 million vehicles

   Use endpoint 1 to get all the MOT history data that you want and use endpoint 3 to maintain the data. Store the data and use daily updates to maintain it, filtering out vehicles you are not interested in.

3. Interested in more than 10 million vehicles and up to all vehicles

   Use endpoint 2 to get the MOT history data for all the vehicles and use endpoint 3 to maintain the data. Store the data and use daily updates to maintain it, filtering out vehicles you are not interested in.

Getting started

All API interfaces are implemented as restful APIs and accessed over https.

To access API you will need an API key that uniquely identifies the source of the request. DVSA will give you an API key if it approves your application.

You should keep your API key secure, as DVSA manages throttling and quotas at an API key level.

Each request must have the following mandatory fields in the header:

• Accept: application/json+v6
• x-api-key: <your api key>

Content-type field confirms that the response type is in JSON format, and the x-api-key field serves your API key to identify the source of the request.

Technical resources

Access the API at https://beta.check-mot.service.gov.uk/

This root URL will change when the service moves from beta to live.

These 4 endpoints equate to the 4 methods of using the API:

1. /trade/vehicles/mot-tests?registration={registration}

   ‘Registration’ is the vehicle registration number.

2. /trade/vehicles/mot-tests?page={page}

   ‘Page’ starts at 0 and ends when you have more than 50,000 pages and 404 Not Found response is returned.

3. /trade/vehicles/mot-tests?date={date}&page={page}

   ‘Date’ is the date of MOT tests and ‘page’ is between 1 and 1440 inclusive.

4. /trade/vehicles/mot-tests?vehicleId={vehicleId}

   'vehicleId' is the unique vehicle ID for vehicles that have had an MOT test.

All pages should be requested daily. Pages without MOT tests will return a 404 Not Found response.

Examples

These examples use the curl command to illustrate how to use the four different methods:

• curl -H "Accept: application/json+v6" -H "x-api-key: <your_api_key>" \https://beta.check-mot.service.gov.uk/trade/vehicles/mot-tests\?registration=ZZ99ABC

  To request the MOT test history for registration ZZ99ABC

• curl -H "Accept: application/json+v6" -H "x-api-key: <your_api_key>" \https://beta.check-mot.service.gov.uk/trade/vehicles/mot-tests\?page=[0-58002]

  (as of 13th July 2017)

  To request a full extract of the database. The last page normally increments by 10 each day.

• curl -H "Accept: application/json+v6" -H "x-api-key: <your_api_key>" \https://beta.check-mot.service.gov.uk/trade/vehicles/mot-tests\?date=20170310\&page=[1-1440]

  To request MOT tests completed on 10 March 2017 from page 1 to 1440.

  Example

  • page 1 shows all tests completed on 10 March 2017 at the 10/03/2017 at 0:01am
  • page 300 shows all tests completed on 10 March 2017 at 5am
  • page 600 shows all tests completed on 10 March 2017 at 10am

• curl -H "Accept: application/json+v6" -H "x-api-key: <your_api_key>" \https://beta.check-mot.service.gov.uk/trade/vehicles/mot-tests\?vehicleId=4Tq319nVKLz+25IRaUo79w==

  To request the MOT test history for a vehicle with the ID '4Tq319nVKLz+25IRaUo79w=='.

Each request returns a JSON document with a collection of vehicles, and each vehicle contains the basic vehicle details and all its past MOT test results.

Reason for rejection types and dangerous defects

The MOT rules changed on the 20 May 2018. This included the way that defects are categorised.

Before 20 May 2018, indicating where a defect was dangerous was an objective and manual process. The ‘dangerous’ property indicates where a defect has been manually marked as dangerous. From 20 May 2018, defect severity is automatically categorised. The RFR property ‘type’ returns the specific defect severity.

Example response

Response codes

A valid request should return a ‘200 - OK’ or a ‘404 - resource not found’ response code:

Possible errors are:

Possible errors are:

Change log

Support

If you have any issues using MOT history API, complete the MOT History Trade API request and support form.

Introduction

The HGV/PSV Operators Annual Test History API provides a mechanism for authorised third-party organisations to access Annual Test History information for HGVs, PSVs and Trailers through an API.

Getting started

All Annual Test History API interfaces are implemented as restful APIs and accessed over https. In order to access the API you will require an API Key that uniquely identifies the source of the request. API Keys should be treated as sensitive information as throttling and quotas are managed at an API Key level.

Each request must have two mandatory fields in the header to enable you to access the data:

• Content-type: application/json
• x-api-key: <your api key>

The first field ensures that the response type is in json format and the second field provides your API key to identify the source of the request. You will not be able to access the API without providing a valid API Key.

Technical resources

Technical documentation will be sent out with your API key, including instructions for how to use it. The technical documentation will include the following:

• the endpoint
• curl command
• example response

Response codes

A valid request should return a ‘200 - OK’ or a ‘404 - resource not found’ response code:

Support

If any issues are experienced using MOT History API service, users are requested to use the following link and select support.

The minimum dataset needs to be provided:

• Name of company
• Name of individual reporting issue.
• Contact E-mail, Telephone,
• Preferred method of contact
• Description of issue.
• Detailed description of issue.

This will generate a ticket in the DVSA Toolset. A member of the DVSA /BJSS support team will pick this up and deal with accordingly.

All issues will be logged as a Priority 3 incident.