Quick Assess API V2

Make every failure actionable and safe.

Use the server request_id and your own safe correlation ID when contacting support. Never send bearer tokens, idempotency secrets or customer claim documents.

Start integration API reference

Status mapping

API status and error handling
Status	Error code	Action
400	`malformed_request`	Correct the request format.
401	`unauthenticated`	Check the server-side bearer credential.
403	`forbidden`	Check token ability, owner, membership and integration status.
404	`resource_not_found`	The resource is unavailable in this integration scope.
409	`idempotency_conflict / vehicle_conflict / report_unavailable`	Resolve the operation-specific conflict.
422	`validation_error / vehicle_identity_conflict`	Correct the submitted values.
429	`rate_limit_exceeded`	Back off and retry later.
500	`internal_error`	Use request_id when contacting support.

Safe retry rules

Retry uncertain state changes with the same idempotency key and identical payload.
Do not retry a terminal failed operation blindly; investigate its request reference.
Poll with exponential backoff and honor poll_after_seconds.
Do not save an error JSON response as a PDF. Validate status, content type and the PDF signature first.

Need access or integration support?

Integration support Contact Quick Assess