Detailed Specifications Data

Use this if you have a configuration to receive detailed specifications

Catalogue Support

The detailed specifications endpoint supports multiple catalogues and their vehicle IDs. Below are the currently supported IDs:

• AutoGrab Vehicle IDs

• Jato Catalogue or Vehicle IDs

If no catalogue identifier is passed in as part of the call, the default is autograb

A vehicle ID can be obtained using any of our vehicle identifications and search endpoints:

• Plain-text Search

• Registration Plate Search

• VIN Search

• Facet Search

The content of a specifications response is bespoke to the agreement you have with AutoGrab. The specific items contained in the specs array will differ based on that agreement, the format remains the same.

Detailed Specifications using AutoGrab ID

curl --location 'https://api.autograb.com.au/v2/vehicles/7837072107620328/detailed-specs?region=au' \
--header 'Apikey: ••••••'

Example Response

{
    "success": true,
    "specs": [
        {
            "category": "Weights",
            "id": "kerb_weight",
            "description": "kerb weight",
            "value": "1442",
            "int_value": 1442,
            "location": null
        },
        {
            "category": "Weights",
            "id": "tare_weight",
            "description": "tare weight",
            "value": "1411",
            "int_value": 1411,
            "location": null
        }
    ],
    "confidence": "standard"
}

The values received for a given specifications call are based on what is contained in the configured API keys contract. In the above example, kerb_weight and tare_weight are returned.

Where relevant, an int_value and a string value for each specification will be returned.

Detailed Specifications with alternative Catalogue Codes

The detailed specifications endpoint will assume the ID being submitted is an AutoGrab vehicle ID unless the feature parameter catalogue .

Detailed Specifications using JATO Codes

When using Jato codes, the catalogue the feature parameter value is required to be set to jato

Example Request

curl --location 'https://api.autograb.com.au/v2/vehicles/2022-831964720220610/detailed-specs?region=au&catalogue=jato' \
--header 'Apikey: ••••••'

Example Response

{
    "success": true,
    "specs": [
        {
            "category": "Version",
            "id": null,
            "description": "Make",
            "value": "Volkswagen",
            "int_value": null,
            "location": null
        },
        {
            "category": "Version",
            "id": null,
            "description": "Model",
            "value": "Polo",
            "int_value": null,
            "location": null
        },
        {
            "category": "Version",
            "id": null,
            "description": "Version",
            "value": "85TSI Comfortline DSG",
            "int_value": null,
            "location": null
        },
        {
            "category": "Version",
            "id": null,
            "description": "Body type",
            "value": "hatchback",
            "int_value": null,
            "location": null
        },
        {
            "category": "Version",
            "id": null,
            "description": "Seating capacity",
            "value": "5",
            "int_value": null,
            "location": null
        },
        {
            "category": "Equipment",
            "id": null,
            "description": "Air Conditioning type",
            "value": "manual",
            "int_value": null,
            "location": null
        },
        {
            "category": "Equipment",
            "id": null,
            "description": "Front and rear power windows",
            "value": "S",
            "int_value": null,
            "location": "F"
        },
    ],
    "confidence": "standard"
}

The response you receive will be defined by the configuration we store for you based on your specific business case. This applies to the inclusion of particular items as well as the inclusion of the "type".