Driver data | INFONITE | Documentation

Your customer’s driving record, from the Spanish traffic authority (DGT).

The licences they hold, their points balance and how that balance has moved. A core signal for mobility, insurance and fleet onboarding. Field by field in Driver.

Requires the driver_data feature

Features are chosen when the execution starts, not here. An execution that did not ask for driver_data answers 204, and the only way to get the data is to run another one.

Status	Meaning
`200`	The driving record.
`202`	`feature_not_ready` — `driver_data` is still running. Only this family waits: the ones that already closed answer now.
`204`	The execution never asked for `driver_data`, or it did and the source had nothing to give. No body either way.
`404`	No execution with that id for your application, or it has been deleted.

Server to server only. This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read.

Your customer's driving record, from the Spanish traffic authority (DGT). The licences they hold, their points balance and how that balance has moved. A core signal for mobility, insurance and fleet onboarding. Field by field in [Driver](/guides/data-models/driver). <Note title="Requires the `driver_data` feature"> Features are chosen when the execution **starts**, not here. An execution that did not ask for `driver_data` answers `204`, and the only way to get the data is to run another one. </Note> | Status | Meaning | | :--- | :--- | | `200` | The driving record. | | `202` | `feature_not_ready` — `driver_data` is still running. **Only this family waits**: the ones that already closed answer now. | | `204` | The execution never asked for `driver_data`, or it did and the source had nothing to give. No body either way. | | `404` | No execution with that id for your application, or it has been deleted. | <Note> **Server to server only.** This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read. </Note>

Authentication

X-APP-SECRETstring

Application Secret

Path parameters

execution_idstringRequiredformat: "object-id"

The execution, as the acceptance response returned it.

Response

200 OK
Your customer’s licence as the traffic authority holds it: the classes they may drive, the dates each was granted and expires, and the points balance where the country runs one.

product"driver_data"

sub_family"driver_data:eu_driver_data"

fetch_datestringformat: "datetime"

Date this product was fetched

countrystringformat: "country"

Country that expired the license.

licenceslist of objects

List of driving licenses.

point_balanceintegerOptional0-20

Balance of the driver in points.

namestringOptional

First name of the driver

name_extrastringOptional

Last name of the driver.

identifierobjectOptional

NIF of the driver.

dangerous_goods_authorizedbooleanOptional

Whether the driver is authorized to transport dangerous goods.

school_transport_authorizedbooleanOptional

Whether the driver is authorized to transport school goods.

addressstringOptional

Address of the driver.

point_movementslist of objectsOptional

List of movements. If not present means the data was not consulted.

Errors

404

Not Found Error

422

Unprocessable Entity Error

Your customer’s driving record, from the Spanish traffic authority (DGT).

The licences they hold, their points balance and how that balance has moved. A core signal for mobility, insurance and fleet onboarding. Field by field in Driver.

Requires the driver_data feature

Features are chosen when the execution starts, not here. An execution that did not ask for driver_data answers 204, and the only way to get the data is to run another one.

Status	Meaning
`200`	The driving record.
`202`	`feature_not_ready` — `driver_data` is still running. Only this family waits: the ones that already closed answer now.
`204`	The execution never asked for `driver_data`, or it did and the source had nothing to give. No body either way.
`404`	No execution with that id for your application, or it has been deleted.

Server to server only. This call is authorised with your application secret: it belongs in your backend, never in a browser, a mobile app or anything your customer can read.