Driver License Verify

Verifies a driver's license number in Nigeria and returns the holder's information including photo and license details.

Endpoint

POST /kyc/nga/driver-license

Authentication

Type	Location	Name
API Key	Header	x-api-key

Request body

Content-Type: application/json

Parameters

Parameter	Type	Required	Description
license_number	string	Yes	Driver's license number.
date_of_birth	string	Yes	Holder's date of birth in format YYYY-MM-DD.
first_name	string	Yes	Holder's first name.
last_name	string	Yes	Holder's last name.

Request example

{
  "license_number": "AAD23208212298",
  "date_of_birth": "1996-05-06",
  "first_name": "Samuel",
  "last_name": "Olamide"
}

Responses

200 Success

Response parameters

Parameter	Type	Description
serviceResultCode	integer	Code that indicates the overall result of the service execution. See Service Result Code
serviceTime	string	Processing time (milliseconds).
serviceResultLog	string	Descriptive field of the result of the service execution. Includes details when there is an error or exception in the module.
serviceTransactionId	string	Transaction identifier associated with the request processed by the API.
data	object	Object with the verified license details. See the table below.

Response parameters — data

Parameter	Type	Description
license_no	string	Verified license number.
first_name	string	Name(s) of the holder.
middle_name	string	Middle name.
last_name	string	Holder's last name(s).
birth_date	string	Date of birth.
gender	string	Gender. Possible values: Male, Female
state_of_issue	string	State that issued the license.
issued_date	string	Issue date.
expiry_date	string	Expiration date.
photo	string | null	Holder's photo in Base64 (can be null).

Service Result Code

The serviceResultCode indicates the overall result of the service execution:

serviceResultCode	Description	HTTP Code
200	The service execution was successful, the module processed the request correctly.	200

Response example

{
  "serviceResultCode": 200,
  "serviceTime": "1800",
  "serviceResultLog": "Success",
  "serviceTransactionId": "f52i346j-45j3-2i4m-i97i-3j792ik33kl",
  "data": {
    "gender": "Male",
    "photo": null,
    "license_no": "AAD23208212298",
    "first_name": "Samuel",
    "last_name": "Olamide",
    "middle_name": "Nomo",
    "issued_date": "2021-10-07",
    "expiry_date": "2026-06-04",
    "state_of_issue": "OYO",
    "birth_date": "1996-05-06"
  }
}

400 Bad Request

Error returned with the service envelope (serviceResultCode reflects the HTTP status code of the response):

{
  "serviceResultCode": 400,
  "serviceResultLog": "Sorry, lookup failed. Please check the details and try again",
  "serviceTime": "151",
  "serviceTransactionId": "08ac9699-dc9e-4cdc-81d7-264f71838309"
}

502 Bad Gateway

Returned when the service is temporarily unavailable or its response could not be interpreted. The body uses the service envelope with serviceResultCode: 500:

{
  "serviceResultCode": 500,
  "serviceResultLog": "Service temporarily unavailable. Please try again later",
  "serviceTime": "3000",
  "serviceTransactionId": "38de2932-0f2h-7gff-14g0-597h04161632"
}

504 Gateway Timeout

Timeout error timeout, returned with the service envelope:

{
  "serviceResultCode": 504,
  "serviceResultLog": "Request timeout. Please try again",
  "serviceTime": "30000",
  "serviceTransactionId": "48ef3043-1g3i-8hgg-25h1-608i15272743"
}

Authentication errors (401/403) are rejected by the gateway before reaching the service and do not use the envelope serviceResultCode. Platform validation errors use the format application/problem+json. See Error handling for details on the three response formats.