> 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/nz-autograb-api-doc/valuation/registration-and-vin-valuations.md).

# Registration & VIN Valuations

Generate a valuation with a Registration Plate or VIN

## Registration Valuation

POST the registration plate and region to `/v2/valuations/registrations/BMT038?`

```json
{
    "region": "nz",
}
```

**Example Response**

```json
{
    "success": true,
    "prediction": {
        "id": "bc3df5a9-0488-4486-acb9-ca22482f127c",
        "vehicle_id": "5804870883868672",
        "kms": 57306,
        "price": 20622,
        "score": 0.9239,
        "retail_price": 20622,
        "trade_price": 17122,
        "adjustment": null
    }
}
```

## VIN Valuation

POST the encapsulated VIN to `/v2/valuations/vins/7AT08G0RX19303899`

```json
{
    "region": "nz",
    "kms": 216000
}
```

**Example Response**

```json
{
    "success": true,
    "prediction": {
        "id": "efa792e6-8071-4289-a5b6-c098ac041702",
        "vehicle_id": "4871414033154048",
        "kms": 216000,
        "price": 9546,
        "score": 0.5407,
        "retail_price": 9546,
        "trade_price": 6205,
        "adjustment": null
    }
}
```

## Implementation Constrains

This integration approach relies on the successful lookup of the vehicle. We recommend staggering your integration so you isolate the vehicle ID first using vehicle search methods and then proceed to valuation driven by the vehicle ID.

This is done to avoid issues where the VIN lookup component of the valuation fails blocking your workflow. In the recommended scenario if your VIN or Rego lookup fails, you can fall back to [Facet](/nz-autograb-api-doc/vehicle-search/facet-search.md) or [Text Search](/nz-autograb-api-doc/vehicle-search/plain-text-search.md) informed by the `"upstream_vehicle"` parameter.


---

# 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/nz-autograb-api-doc/valuation/registration-and-vin-valuations.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.