Registration & VIN Valuations

Registration Valuation

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

{
    "region": "nz",
}

Example Response

{
    "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

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

Example Response

{
    "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 or Text Search informed by the "upstream_vehicle" parameter.