Skip to main content
Base URL: https://api.trycarhub.com The generated API reference is the source of truth for every operation, field and schema.

Browse API endpoints

Use Mintlify’s generated OpenAPI reference, including schemas, examples and request playgrounds.

​
Find the right endpoint

Use the API reference’s tag groups to browse by capability:

​
Inference endpoints

CarHub provides 24 POST inference endpoints across vehicle understanding, condition, parts, pricing, image production and presentation. It also offers the inspection bundle, jobs, uploads and an endpoint catalogue. All /v1/* calls use an API key. Requests normally respond 202 Accepted with a job. Fast endpoints may return 200 OK when called with wait=true.

​
Request conventions

  • Use JSON unless an endpoint accepts a file directly; use multipart/form-data for direct binary input.
  • Send Idempotency-Key with every POST.
  • Read Request-Id from every response and include it in support requests.
  • Honor Retry-After and the RateLimit-* headers after 429 responses.
  • Keep opaque IDs (job_…, upl_…, key_…, whe_…) intact; never parse or fabricate them.
Use the generated reference for endpoint-specific request bodies and responses. The error guide explains shared failure handling, and the jobs guide explains how to retrieve results.