DealerMAX Developers

Error catalog

This catalog lists the error classes integrators should handle when calling the read-only Dealer Public API on catalog.dealermax.app. The API is intentionally small: authentication, parameter validation, dealer-scoped not-found responses, rate limits, and temporary service failures.

code	status	title
`missing_api_key`	401	Missing API key
`invalid_api_key`	401	Invalid API key
`expired_api_key`	401	Expired API key
`invalid_service`	400	Invalid service
`invalid_content_type`	400	Invalid content type
`invalid_identifier`	400	Invalid identifier
`dealer_not_found`	404	Dealer profile not found
`vehicle_not_found`	404	Vehicle not found
`offer_not_found`	404	NLT offer not found
`content_not_found`	404	Content not found
`validation_error`	422	Validation failed
`rate_limited`	429	Rate limit exceeded
`service_unavailable`	503	Service unavailable
`internal_error`	500	Internal error

Problem Details envelope

HTTP/1.1 401
Content-Type: application/problem+json
X-Request-ID: req_...

{
  "type": "https://developers.dealermax.app/errors/missing_api_key",
  "title": "Missing API key",
  "status": 401,
  "code": "missing_api_key",
  "detail": "Missing API key",
  "request_id": "req_..."
}

Every Dealer Public API error type is dereferenceable. The required fields are type, title, status, and code. Responses can also include detail, request_id, and for validation failures an errors array. Capture the X-Request-ID header when contacting support.

Use Retry-After on rate-limit responses, retry only safe GET requests, and never expose the API key in browser JavaScript.

Authoritative reference: https://developers.dealermax.app/api Contact: support@dealermax.app Owner: Azure S.r.l.