> For the complete documentation index, see [llms.txt](https://devhub.autograb.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devhub.autograb.com/vehicle-search/vehicle-search-features.md).

# Vehicle Search Features

Add on additional data into your VIN or Registration plate searches.

When making a [VIN](https://devhub.autograb.com/vehicle-search/vin-search.md) or [Registration Plate](https://devhub.autograb.com/vehicle-search/registration-plate-search.md) search you can request more data than the standard payload by leveraging a range of features described below. You can request on or many of the features at once as a comma separated list.&#x20;

{% code overflow="wrap" %}

```json
curl --location 'https://api.autograb.com.au/v2/vehicles/vins/JTDKW3D380D521439?features=writeoff_info%2Cregistration_status%2Cextended_data&region=au' \
--header 'ApiKey: YOURKEY'
```

{% endcode %}

{% hint style="info" %}
Ensure your commercial agreement has these features enabled if you require them.
{% endhint %}

### **Extended Data**

This feature will return an extended payload of vehicle data from the registration authority. Use `features=extended_data` to receive this payload.

```json
   "extended_data": {
        "body_type_description": "CAR/SEDAN",
        "color_description": "WHITE",
        "engine_number": "DKJ039523",
        "make_code": "VOLKS",
        "make_description": "",
        "model_code": "",
        "model_description": "POLO",
        "vehicle_type_description": "CAR / SMALL PASSENGER VEHICLE"
```

### **Upstream Data**

This feature will return structured descriptive data from the registration authority. Use `features=additional_upstream_data` to receive this payload.

```json
    "additional_upstream_data": {
        "vin": "WVWZZZAWZKU065305",
        "year": "2019",
        "make": "Volkswagen",
        "model": "Polo",
        "badge": "AW",
        "series": "85TSI Comfortline",
        "fuel_type": "95 RON PULP",
        "body_style": "Hatch",
        "transmission": "7 auto",
        "capacity_cc": "1000",
        "colour": "White",
        "title": "2019 Volkswagen AW Polo 85TSI Comfortline 4 Hatch 7sp auto 1.0L 1000cc 3cyl T/Petrol 2018"
```

### **Vehicle Age**

This feature will return structured data on the age of a vehicle from the registration authority. Use `features=vehicle_age` to receive this payload.

```json
    "vehicle_age": {
        "compliance_plate": "2019-04",
        "year_of_manufacture": 2019
```

### **Writeoff Information**

This feature will return information about the write-off status of a vehicle. Use `features=writeoff_info`

```json
  "writeoff_info": {
        "incident_list": [
            {
                "code": "Repairable Write-off",
                "damage_codes": "I04AI17DI21C",
                "jurisdiction": "VIC",
                "recorded_date": "2024-04-28",
                "type_code": "Collision"
            }
        ]
```

The Australian Government publishes the full list of write-off codes [on the PPSR website](https://www.ppsr.gov.au/searching/do-used-car-or-vehicle-search/understand-your-car-search-result/understanding-written-codes). It covers:

* the 2 write-off types (statutory and repairable)
* incident type codes (letters D, F, H, I, M and W)
* damage location codes (numbers 1 to 46)
* damage severity codes (letters A to P)

Each write-off record combines these into a single code. For example, `I01B` means Impact, Passenger front, Light panel.

### **Stolen Status**

This feature will return information about the statutory stolen status of the vehicle. Use `features=stolen_info`

```json
      "stolen_info": {
        "incident_list": [
            {
                "incident_type": "Plate",
                "jurisdiction": "VIC",
                "reported_date": "2026-04-14",
                "summary": "POL JUR-V REF-VS260019505"
            }
        ]
```

Stolen data doesn't use a code list. Instead, a result is either:

* not recorded as stolen
* a stolen notification

Each notification relates to a VIN, plate, chassis or engine number. It includes the state or territory that reported it, the date and a police reference number. When the vehicle is recovered, the police notify their jurisdiction and the stolen flag is removed.

{% hint style="info" %}
NEVDIS stolen data doesn't include Tasmanian vehicles.
{% endhint %}

### **Performance Information**

This feature will return information about the high performance status of the vehicle. Use `features=performance_info`

```json
    "performance_info": {
        "power_kw": 183,
        "weight_tonnes": 2.397,
        "power_to_weight_ratio": 76
    }
```

### **Registration Status**

This feature will return information about the registration status of a vehicle. Use `features=registration_status`

```json
    "registration_status": {
        "expiry_date": "2024-09-06",
        "status": "REGISTERED"
    }
```

### Plate Type

This feature will return information about the plate type of the vehicle registration. Use `features=plate_type`

```json
    "plate_type": {
        "plate_type": "Standard",
        "plate_type_code": "S"
    }
```

### **Build Data**

This feature will return the options fitted to the vehicle based on your [Factory Build Data](https://devhub.autograb.com/vehicle-data/factory-build-data.md). It will show all options, the price and if it is fitted to the vehicle or not. Use `features=build_data`

```json
"build_data": {
        "vin": "WAUZZZ8V7K1028938",
        "make": "AUDI",
        "model": "A3",
        "features": [
            {
                "code": "0A1",
                "value": "2 doors"
            },
            {
                "code": "0AE",
                "value": "Front stabilizer bar"
            },
            {
                "code": "0B2",
                "value": "Wheelbase"
            },
        ],
        "build_date": "2019-03-20"
```

{% hint style="info" %}
Refer to [Factory Build Data](https://devhub.autograb.com/vehicle-data/factory-build-data.md) reference material for more information on supported OEMs.
{% endhint %}

### **VIN Build**

This feature will return the date the vehicle was built at the factory. Use `features=vin_build` to receive this payload.

```json
    "vin_build": {
        "build_date": "2021-12-01"
    }
```

If we don't have a build date for the VIN, `vin_build` is `null`.

### **VIN Paint**

This feature will return the factory paint code, colour, finish and description of the vehicle. Use `features=vin_paint` to receive this payload.

```json
    "vin_paint": {
        "paint_code": "070",
        "paint_colour": "Pearl White",
        "paint_type": "Pearlescent Paint",
        "paint_description": "Pearl White"
    }
```

`paint_type` is the finish, such as Solid Paint, Metallic Paint, Pearlescent Paint or Two Tone Paint. Any field can be `null`; many records have a paint code and colour but no paint type. If we don't have any paint details for the VIN, `vin_paint` is `null`.

Consider pairing with a [vehicle stock imagery](https://devhub.autograb.com/vehicle-data/stock-photos.md) to deliver a refined and user friendly interface.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://devhub.autograb.com/vehicle-search/vehicle-search-features.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
