Access to Driver Data (ADD)
Frequently Asked Questions
1. What is the ADD service used for?
ADD is a real time access service to organisations who have a demonstrable business need to check the driving entitlement and endorsement record of drivers. Data is supplied on the explicit basis that it must not be used for identity checking of any kind and is only used to check entitlement to drive where there is a legitimate need to do so.
2. Is the ADD service available over the web?
No. The ADD service is available via cloud-hosted API.
3. What’s an API?
An application programming interface (api) is a software interface that allows two applications to interact with each othe r without any user intervention.
4. How will we be able to enquire on dvla data?
You will need to develop your own systems/portals, thatll interact with the api to return an enquiry response.
5. Will you provide a front-end system to enable me to display the result of a driver check?
No, the ADD service will only provide the raw data in the return in the format of JSON. You will be required to build a front-end system if you wish to interpret this data in a user-friendly interface.
6. Can I use the service to enquire on anyone?
No, all enquiries will need to be supported by a fair processing declaration that has been signed by the data subject. DVLA offers a standard Data Protection Declaration (D906/ADD) which DVLA recommend you use.
7. What are the associated costs for the ADD service?
The only applicable costs will be a £0.60p fee per successful enquiry, this is reviewed annually.
8. How are enquiries billed/paid?
You will need to set up a direct debit mandate and enquiries are billed monthly. There is no alternative method for payment.
9. Is the service available 24/7?
Yes, the service is real-time and available 24/7.
10. What is the throttle limit for enquiries?
The throttle limit is 10 per second.
11. What knowledge will I need to implement the ADD service?
You will need to ensure that you have the technical resource capable of setting up, managing and problem-solving issues. There is a developer portal users can access directly at https://developer-portal.driver-vehicle-licensing.api.gov.uk/apis/driver-view/driver-view-description.html.
12. If there are changes to my business, do I need to notify you?
Any changes to your business which impacts the ADD service would need to be highlighted in advance as set out in the ADD Contract.
13. What do I need to do after being onboarded to the API?
Once set up, you will be sent an email to update the one-time password within 24hrs of receipt of the email.
14. What is meant by the code ENQ037 – record for supplied driving licence number not available for enquiry via this service?
The ENQ037 is the error code we return when a record has been suppressed in our API, this could be for several reasons and consumers should be aware that some of our records will be suppressed.
15. Does the service provide historic data on a driver?
Following discussion, it was agreed where the licence status is Valid there is benefit in returning details of expired and lapsed driving entitlements in addition to valid category, as this demonstrates driving and road going experience. A driver may have a recent test pass in a category but held that previously, albeit with restrictions possibly.
16. In the new service entitlements.categoryType can be “Provisional” or “Full”. In the old API the entitlements.type can be “P”, “F” or “U”. “P” corresponds to “Provisional” and “F” to “Full” but there is no equivalent to “U” (Unclaimed) in the old ADD service.
If a test has been passed in a category but is yet to be claimed by the driver, test pass data will be returned. This is equivalent to “U” (unclaimed) in the old service. entitlements.categoryType will continue to be returned as “Provisional” until the driver has returned their licence to claim the test pass.
17. If the licence validFromDate in the ADD OSL response is prior to 19th Jan 2013 (i.e. pre EU 3rd Directive) has mapping been carried out by DVLA as the 3rd directive entitlements are returned?
Yes. If the licence was issued under an older directive e.g. groups and pre 3rd directive then DVLA has mapped the entitlements displayed on the physical licence to 3rd directive categories.The web page “Compare old and new driving licence categories” (https://www.gov.uk/old-driving-licence-categories) can be referenced to help users understand any differences between the entitlements and restrictions printed on their physical licence and the entitlements and restrictions returned by the new ADD system.
To reiterate all entitlements returned via the new API are 3rd directorised (legacy directiveIdentifier 4)
18. Will reference lists of entitlement and restriction codes be maintained and kept up to date in the appendices to the ADD OSL specification?
DVLA will not maintain appendices as the new ADD service returns both the code and literals e.g. category code and category legal literals. If any additional entitlements, restriction codes or endorsements are introduced following legislative changes we will share these with you in advance via the normal communication email.
19. Are all new ADD OSL entitlements 3rd Directive licences (Directive Indicator 4)?
Yes, all entitlements are returned as directive indicator 4 in the new ADD service. These are the EU 3rd directive entitlements which came into being on 19 January 2013. If the licence validFromDate in the ADD OSL response is prior to 19th Jan 2013, so pre 3rd Directive, mapping will have taken place at DVLA so they are shown as 3rd directive categories. The web page “Compare old and new driving licence categories” (https://www.gov.uk/old-driving-licence-categories) can be referenced to help users understand any differences between the entitlements and restrictions printed on their physical licence and the entitlements and restrictions returned by the ADD OSL system.
20. Why are expired and lapsed categories returned in addition to current entitlements? Or more than one valid entitlement for the same category when the previous ADD service only returned current categories?
By returning details of previous entitlements held by the driver this demonstrates the driver’s overall driving experience e.g. they may have held automatic car entitlement for some years but only recently passed the same manual category. Or they may have driven a heavier category for some years with a restriction e.g. not for hire or reward before only recently passing the same category without restriction.
21. Endorsement disqualification end date. The new API seems to define the disqualification duration as a period starting from the day of conviction (endorsement.convictionDate)
Overall ‘disqualifiedUntil’ date is returned in the new API. If only one disqualification is held then that will be the endorsement.disqualification end date. However, more than one disqualification may be held concurrently in which case disqualifiedUntil date refers to the longest of these disqualifications.