Is this a developer portal?

No. This is the public product page. Interactive Swagger, OpenAPI JSON, and endpoint details live on the API docs host.

Can browser code call the external API directly?

No. Customer API keys belong on your server, worker, server-side job, or trusted integration service.

Does the API replace auction due diligence?

No. It normalizes public auction data and freshness signals, but buyers still need source review, inspection, and compliance with auction rules.

What should I use for ongoing sync?

Use cursor-based change feeds for batch sync and webhooks for event-driven workflows. Avoid full rescans as the default pattern.

Normalized Copart and IAAI auction data for your internal systems

Use one REST API for search, lot detail, VIN context, signed media, reference dictionaries, incremental change feeds, and signed webhooks. The page explains the product; the full interactive reference stays on the API docs host.

Create account View docs See API pricing

Integration contract

A short version of the contract before your developer opens Swagger.

Format

REST + OpenAPI 3.1

Plain HTTP endpoints, cursor pagination, stable response shapes, and a machine-readable spec.

Freshness

Active lots under 30 minutes

Freshness is surfaced as a product signal where source timing is available.

Semantics

Closed enums + provenance

Damage, title, keys, transmission, and source fields are normalized instead of passed through as raw strings.

The endpoints teams usually need first

The API is designed for dealer CRMs, pricing tools, lead portals, analytics jobs, and internal buying desks that do not want to operate their own auction ingestion stack.

Search

GET /v1/lots

Filter inventory by source, market, year, make, model, sale window, title, damage, and other normalized criteria.

Lot detail

GET /v1/lots/{id}

Read canonical lot fields, sale state, bid context, media references, source identifiers, and freshness metadata.

VIN context

GET /v1/vin/{vin}

Connect vehicle identity, source matches, sale attempts, title signals, and available history into one response.

Change feed

GET /v1/changes

Sync incremental lot updates by cursor instead of rescanning the full catalog on every job.

Webhooks

POST /v1/webhooks

Receive signed events for matching lots, sale changes, price movement, and lifecycle updates.

Reference data

GET /v1/reference/*

Use source dictionaries and normalized enums in your own filters, forms, and downstream validation.

Start small, then raise limits when the integration proves value

Live plan values are read from the server plan catalog.

Full pricing

API Basic

5k req/day, no webhooks

$29/mo

$50 balance included

Requests/day: 5,000
API keys: 2
Webhooks: None

API Basic (annual)

5k req/day, no webhooks. Billed annually.

$290/mo

$50 balance included

Requests/day: 5,000
API keys: 2
Webhooks: None

API Pro

50k req/day + webhooks

Recommended

$99/mo

$500 balance included

Requests/day: 50,000
API keys: 10
Webhooks: 50

API Pro (annual)

50k req/day + webhooks. Billed annually.

Recommended

$990/mo

$500 balance included

Requests/day: 50,000
API keys: 10
Webhooks: 50

API Max

High volume, webhooks unlimited

$299/mo

$2,500 balance included

Requests/day: Custom
API keys: 50
Webhooks: Custom

API Max (annual)

High volume, webhooks unlimited. Billed annually.

$2,990/mo

$2,500 balance included

Requests/day: Custom
API keys: 50
Webhooks: Custom

Practical integration notes

The API page should qualify the integration before a developer opens Swagger.