CARS
/
2. Retrieve details
Last updated

Retrieve car details

Understand the /cars/details endpoint, required fields, optional filters, best practices, and common use cases.

→ Use the /cars/details endpoint to fetch comprehensive information about a specific car or a list of cars.

This data is typically displayed on the car details page or in search results, allowing travellers to see full specifications before booking.

Use cases

  • Display car details in search results or on the car page.
  • Preload static car information to enhance UI performance.
  • Build local caches of car specifications to reduce API calls.
  • Show travellers features, fuel type, transmission, and images for better booking decisions.

Create the request body

To obtain details for specific cars:

  1. Optionally, filter by last_modified to retrieve only cars updated recently.
  2. Specify maximum_results per request.
  3. Use page if you need to paginate through large sets of results.

Example - Retrieve all cars updated after a specific date:

{
  "last_modified": "2025-10-17T11:05:00+00:00",
  "maximum_results": 50
}

Note: last_modified must be in ISO 8601 format with UTC offset.

Example response

The returned response includes static information for each car, such as capacity, features, make, model, fuel type, transmission, supplier, and images.

{
  "request_id": "01fr9ez700exycb98w90w5r9sh",
  "data": [
    {
      "id": 37715,
      "capacity": {
        "bags": { "large": 1, "small": 1 },
        "doors": "4/2",
        "seats": "4+2"
      },
      "country": "es",
      "features": ["air_conditioning", "all_wheel_drive"],
      "image": "https://example.com/image.jpg",
      "make": "hyundai",
      "model": "elantra",
      "specification": {
        "code": "ECAR",
        "description": "economy",
        "fuel": "petrol",
        "transmission": "automatic"
      },
      "supplier": 423
    }
  ],
  "metadata": {
    "next_page": null
  }
}

Returned car details

The resulted vehicle details include:

Key parameters
idThe car's unique identifier (id).
capacitySpecifies the number of bags, seats, and doors for each car.
featuresFeatures like air conditioning and all wheel drive.
imageURL to car image (JPG).
make/ modelThis is the brand and the vehicle model.
SpecificationACRISS code and description, fuel type, and transmission:
  • code - Standard Interline Passenger Procedure (SIPP) code, which is four-letter abbreviations that identify the major features of a rental car (See the full list here).
  • description - Category description (e.g. economy) (See the full list here).
  • fuel - electric, petrol, hybrid, diesel, etc.
  • transmission - if automatic or manual.
SupplierYou can use this ID to obtain further details about a specific supplier.
next_pagePagination token for next page results. See pagination guide

Store car details

Most car details rarely change, and are considered static data. To improve performance and reduce latency:

  • Store the response from /cars/details in your system.
  • Serve cached details in subsequent requests (search results, car pages).
  • Refresh your cache periodically or when relevant updates are detected, such as new images, updated specifications, or changes to availability.
  • Storing reduces API calls and ensures faster page loads, improving the user experience.
Important

Follow the Car rental static data guide for best practices.

Best practices

✓ Use last_modified to fetch only updated cars and optimise API usage.

✓ Use maximum_results and page for large datasets.

✓ Always include your X-Affiliate-Id in the request header to ensure correct attribution.

✓ Store static results (capacity, make/model, fuel, images) for faster page loads.

✓ Include car images and specifications in your UI for a richer traveller experience.

Curious to know more?
Previous page
Next page