API Test Cases
Test your requests in a safe zero-cost way through our test case set.
You can use our test cases to confirm your implementation on our production endpoints. All requests using these values are not billable.
Test Cases
Refer below to set of test cases. They are all linked and refer back to the same vehicle IDs.
Type | Region | Value | Outcome |
---|---|---|---|
Registration Plate | Australia |
| Returns a successful lookup response with a high-quality vehicle match for an ICE vehicle |
Registration Plate | Australia |
| Returns a successful lookup response with a high-quality match for an EV |
Registration Plate | Australia |
| Returns a successful lookup response with a low-match quality warning |
Registration Plate | Australia |
| Returns the VIN and vehicle description but no matching vehicle |
Registration Plate | Australia |
| Only returns the VIN and no other vehicle details |
VIN | Australia | 00000000000000000 | Returns a valid VIN match in Australia for an ICE vehicle |
VIN | Australia | 00000000000000010 | Returns a valid VIN match in Australia for an EV |
Vehicle ID | Australia | 1111111111111111 | Can be used for /Predict or /Sourcing to return outcomes. |
Supported Endpoints
Test cases are supported across a range of API endpoints listed below. If the endpoint you are testing with is not listed get in touch to request test data.
/valuations/predict
/valuations/vins
/valuations/registrations
/valuations/residual
/valuations/predict/conditions
/sourcing/market_overlay
/sourcing/market_overlay/statistics
Implementation Guide
An example implementation could run a test as part of an integration test or development process. For example, you could test a valuation flow by first using a registration plate to get the ID (which is also test data) and send that to a /predict to get a valuation and a market overlay.
Last updated