Agree the scope
Map vehicle identifiers, target markets, usage and display requirements before connecting systems.
CarPriceLab / Valuation API
The same intelligence.
Inside your own product.
CarPriceLab valuation can be integrated into automotive software, dealer systems and independent platforms through an API. Discuss access and the integration scope with us.
INTEGRATION ACCESS / BY ARRANGEMENTVehicle details in.
Vehicle details in.
Market context out.
Use the valuation behind CarPriceLab reports in your own workflow. A useful integration carries the range and its evidence together, not just a headline price.
- Make, model, year and mileage
- Fuel, transmission, power and battery details
- Optional preferred country
- Netto by default; optional brutto with an explicit VAT rate
The versioned API uses HTTPS and Bearer authentication. Access and commercial terms are agreed individually; API keys are issued by CarPriceLab. Keep your key on your server, never in browser code.
Independent by design
Your platform.
Your workflow.
CarPriceLab is not tied to an auction, a marketplace or a sales channel. Use a market reference wherever vehicle value informs a decision.
Coverage depends on available comparables. A missing estimate is a meaningful outcome, not a zero valuation.
Understand the calculation ↗API v1 / HTTPS + JSON
A small, consistent interface.
| Endpoint | Purpose |
|---|---|
GET /api/v1/catalog | Supported makes, models, fuels, transmissions and markets. |
POST /api/v1/valuations | Retail and wholesale estimates for your vehicle specification. |
POST /api/v1/reports | Create a shareable report. Send an Idempotency-Key to safely retry. |
DELETE /api/v1/reports/:key | Revoke a report belonging to your account. |
Use catalogue identifiers in requests. Monetary values are in EUR. A 200 response can report insufficient evidence; 401/403 indicate access issues, 422 indicates invalid input, 429 asks you to retry later, and 503 indicates a temporary service failure. Never replace a saved valuation with a network error.
Valuation data
What the result contains.
| Data group | Meaning |
|---|---|
| Availability | Whether the vehicle can be valued; an insufficient-data result when the sample is too small. |
| Retail reference | Estimated retail market value and P25–P75 asking-price range, with the selected market and VAT basis. |
| Wholesale reference | Estimated wholesale value derived from the retail distribution. Client-facing results include both estimates together, or an insufficient-evidence status. |
| Market evidence | Selected comparable count, represented countries and the estimated retail range. Shared reports provide the supporting market analysis. |
| Shareable reports | Create an independent report link with vehicle details and your business contact. Revoke the link when it should no longer be available. |
| Traceability | Report reference, methodology version, target market and observation period. |
| Reliable integration | Scoped API keys, per-key request limits, stable error codes and idempotent report creation. |
Validate real coverage
Evaluate your vehicle mix, inspect insufficient-data cases and retain the basis and limitations alongside every price.
Define operations
Confirm access controls, quotas, retention, refresh policy, support and commercial terms for your integration.
Your next decision, better informed.
Bring context
to your workflow.
Tell us what you buy, value or build.
Let’s shape the right approach.