DVLA Authentication API
- URL
-
https://driver-vehicle-licensing.api.gov.uk/thirdparty-access - Spec
- https://developer-portal.driver-vehicle-licensing.api.gov.uk/apis/authentication-api/authentication-api.json
- Docs
- https://developer-portal.driver-vehicle-licensing.api.gov.uk/apis/authentication-api/authentication-api-description.html
api_key=<credential> For secure DVLA APIs, onboarding supplies a username and one-time password, as described in the Authentication API guide. First change the one-time password using the Authentication API, then use the resulting username and password to call the authenticate endpoint and obtain a JWT.
x-api-key: <credential> + DVLA JWT ID token Authorization: <credential> discovered DVLA issues API keys during onboarding. For secure APIs, the Authentication API guide says a username, one-time password, API key and API URLs are supplied as part of the onboarding process; for KADOE use the KADOE registration page to apply. For VES, the guide says registration is currently closed and the issued key must be sent in x-api-key.
Use the DVLA Authentication API with your onboarded DVLA username and password to obtain an id-token JWT, which expires after 1 hour. Then send that JWT in the Authorization header when calling secure DVLA APIs that require the secure API pattern.