For developers and software companies
Two services, one integration: a valuation engine and a normalised vehicle catalogue. JSON over HTTPS, documented endpoints, free sandbox before any commitment.
First request
Authentication and a valuation call
valuation.sh
curl -X POST https://api.datadeger.com/v1/valuation \
-H "Authorization: Bearer $DD_SANDBOX_KEY" \
-H "Content-Type: application/json" \
-d '{
"brand": "Ford",
"model": "Focus",
"year": 2020,
"km": 96000
}'
Reference
Main endpoints
| Method | Path | Purpose |
|---|---|---|
| POST | /v1/valuation | Value a single vehicle |
| POST | /v1/valuation/bulk | Value up to 500 vehicles in one call |
| GET | /v1/catalogue/brands | List makes |
| GET | /v1/catalogue/models | List models for a make |
| GET | /v1/catalogue/trims | List trims and engines |
| POST | /v1/webhooks | Register a price-change webhook |
Production notes
What to expect in production
- Auth — Bearer tokens, separate sandbox and production keys, optional IP allow-listing.
- Rate limits — Documented per plan; limit headers returned on every response.
- Latency — Single valuation typically responds well under a second.
- Errors — Consistent error envelope with machine-readable codes.
- Confidence — Every valuation includes a confidence score and sample size — surface it in your UI.
- Data handling — Query contents are not used to train models; only aggregate service metrics are kept.
Licensing
White-label use
If you are embedding valuation into your own product, white-label licensing is available: your branding, your UI, our data. Enterprise plans also cover project-specific model calibration and an SLA on response times.
Documentation, code samples and a Postman collection are provided with sandbox access.
Request sandbox access
Tell us roughly what you are building and expected query volume. Sandbox keys are free and issued quickly.