Owned vehicles | INFONITE

[
  {
    "product": "driver_data",
    "sub_family": "driver_data:eu_owned_vehicle",
    "fetch_date": "2026-09-12T01:26:48+00:00",
    "country": "ES",
    "registration_date": "2011-08-04",
    "inspection_expiry_date": "2027-07-07",
    "inspection_pending": false,
    "license_plate": "0000AAA",
    "administrative_situation": "FAVORABLE",
    "vin": "11111111111111111",
    "make": "AUDI",
    "model": "A4",
    "mileage": 122623,
    "fuel_type": "DIESEL",
    "emission_class": "ES:B",
    "insurance": {
      "is_active": true,
      "company": "MUTUA MADRILEÑA AUTOMOVILISTA",
      "start_date": "2016-02-19"
    },
    "simple_vehicle_report": {
      "report_date": "2026-09-12T01:26:48+00:00",
      "has_incidents": false
    }
  },
  {
    "product": "driver_data",
    "sub_family": "driver_data:eu_owned_vehicle",
    "fetch_date": "2026-09-12T01:26:48+00:00",
    "country": "ES",
    "registration_date": "2024-11-20",
    "inspection_expiry_date": "2028-11-20",
    "inspection_pending": true,
    "license_plate": "0000BBB",
    "administrative_situation": "FAVORABLE",
    "vin": "00000000000000000",
    "make": "TOYOTA",
    "model": "YARIS",
    "fuel_type": "GASOLINA",
    "emission_class": "ES:ECO",
    "insurance": {
      "is_active": false,
      "company": "MAPFRE ESPAÑA",
      "start_date": "2024-11-20"
    },
    "simple_vehicle_report": {
      "report_date": "2026-09-12T01:26:48+00:00",
      "has_incidents": true
    }
  }
]

The vehicles registered to your customer, from the Spanish traffic authority (DGT).

One entry per vehicle: identification, insurance situation, roadworthiness inspection and administrative state. Field by field in Vehicles.

It reads both ways. As asset verification — what they own — and as a liability check: an uninsured vehicle, or one overdue for inspection, shows up here.

Requires the vehicles_data feature

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

Status	Meaning
`200`	The vehicles.
`202`	`feature_not_ready` — `vehicles_data` is still running. Only this family waits: the ones that already closed answer now.
`204`	The execution never asked for `vehicles_data`. No body.
`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.

The vehicles registered to your customer, from the Spanish traffic authority (DGT). One entry per vehicle: identification, insurance situation, roadworthiness inspection and administrative state. Field by field in [Vehicles](/guides/data-models/vehicles). <Tip> **It reads both ways.** As asset verification — what they own — and as a liability check: an uninsured vehicle, or one overdue for inspection, shows up here. </Tip> <Note title="Requires the `vehicles_data` feature"> Features are chosen when the execution **starts**, not here. An execution that did not ask for `vehicles_data` answers `204`, and the only way to get the data is to run another one. </Note> | Status | Meaning | | :--- | :--- | | `200` | The vehicles. | | `202` | `feature_not_ready` — `vehicles_data` is still running. **Only this family waits**: the ones that already closed answer now. | | `204` | The execution never asked for `vehicles_data`. No body. | | `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
Vehicles registered in your customer’s name: plate, make, model, registration date and the administrative state the register reports for each one.

An empty list is an answer, not a gap: the feature ran and the source reported none.

product"driver_data"

sub_family"driver_data:eu_owned_vehicle"

fetch_datestringformat: "datetime"

Date this product was fetched

countrystringformat: "country"

Country where the vehicle is registered.

registration_datedate

Registration date of the vehicle.

inspection_expiry_datedateOptional

inspection_pendingbooleanOptional

If true, the vehicle has failed the previous inspection or is pending to be inspected.

license_platestringOptional

License plate number of the vehicle.

administrative_situationstringOptional

Current administrative situation of the vehicle.

vinstringOptional

Vehicle Identification Number.

makestringOptional

Vehicle manufacturer.

modelstringOptional

Vehicle model name.

trimstringOptional

Specific vehicle trim/variant.

colorstringOptional

Color of the vehicle.

mileageintegerOptional>=0

mileage_datedateOptional

Date when the mileage was recorded.

fuel_typestringOptional

Fuel type of the vehicle.

emission_classstringOptional

Emission class of the vehicle.

insuranceobjectOptional

Vehicle insurance policy.

simple_vehicle_reportobjectOptional

Simple vehicle report.

Errors

404

Not Found Error

422

Unprocessable Entity Error

The vehicles registered to your customer, from the Spanish traffic authority (DGT).

One entry per vehicle: identification, insurance situation, roadworthiness inspection and administrative state. Field by field in Vehicles.

It reads both ways. As asset verification — what they own — and as a liability check: an uninsured vehicle, or one overdue for inspection, shows up here.

Requires the vehicles_data feature

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

Status	Meaning
`200`	The vehicles.
`202`	`feature_not_ready` — `vehicles_data` is still running. Only this family waits: the ones that already closed answer now.
`204`	The execution never asked for `vehicles_data`. No body.
`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.