> 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/valuation-predictions.md).
# Valuation Predictions
Generate market accurate predictions for vehicles.
## Overview
The Valuation API can be used to determine the present retail & trade values, as well as the residual values of new vehicles.
This API requires [authentication](https://docs.autograb.com.au/guide/auth/) and an appropriate license attached to it.
To use the API, a Vehicle ID returned from the Vehicle Search API or Vehicle Facet API is required.
## Example
**Request**
{% hint style="info" %}
To retrieve a Vehicle ID, use the [Vehicle Search APIs](https://docs.autograb.com.au/guide/vehicle/).
{% endhint %}
Starting with a vehicle ID post it to /v2/valuations/predict
```json
{
"region": "nz",
"vehicle_id": "5804870883868672"
"kms": 30000,
"condition_score": 2
}
```
{% hint style="info" %}
The [condition score](#condition-score) is optional and can be used to further refine your pricing prediction.
{% endhint %}
**Payload**
```json
{
"success": true,
"prediction": {
"id": "a2955915-9611-40ef-8b98-b827dad76ff4",
"vehicle_id": "5804870883868672",
"kms": 57306,
"price": 20622,
"score": 0.9239,
"retail_price": 20622,
"trade_price": 17122,
"adjustment": null
}
}
```
#### Pricing ID
The payload returned by price prediction requests will include an ID, which you can use to refer to the pricing request in the future. The `/v2/valuations/history/{PRICING_ID` method will return the response from a previous pricing request, and you can also use the Pricing ID to track price changes with the **Price Changes API**, if licenced.
To get a paginated list of all your previous price predictions, you can use the `/v2/valuations/history` endpoint.
#### Condition Score
By supplying a condition score, you can manipulate the `trade_price` returned by the prediction endpoint. The condition score can be between `1` and `5`. A condition of `1` being poor condition and a condition of `5` excellent condition.
Supplying any other numbers will return the default `trade_price` which assumes excellent condition.
If you're building a user interface where you allow the user to choose a condition it is recommended you follow the industry standard in the table below.
| Condition | Condition Score |
|---|
| Poor | 1 |
| Fair | 2 |
| Average | 3 |
| Good | 4 |
| Excellent | 5 |
---
# 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/valuation-predictions.md?ask=&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.