/copart/lots

POST /api/copart/lots

Price: 5 credits

Get one Copart vehicle lot by lot number: vehicle specs, title and damage, the condition-report damage items with photos, current bid and sale status, auction date, yard and AutoCheck summary.

How to use it

Inspect one salvage or wholesale lot before bidding: damage items, title, odometer and the live bid state. Pass an id from copart/lots/search; copart/lots/images returns the full photo set.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lot string required — Copart lot number or a copart.com lot URL (examples: "72318225", "https://www.copart.com/lot/72318225/salvage-2020-land-rover-defender-pa-pittsburgh-north"; minLength: 1)

Response

• @type string (default: "CopartLot")
• id string required
• url string required
• alias string nullable
• year integer nullable
• make string nullable
• make_code string nullable
• model string nullable
• model_group string nullable
• model_detail string nullable
• trim string nullable
• vin_masked string nullable
• vehicle_type string nullable
• vehicle_type_code string nullable
• vehicle_category_code string nullable
• body_style string nullable
• color string nullable
• exterior_color string nullable
• interior_color string nullable
• engine string nullable
• cylinders string nullable
• fuel_type string nullable
• drive string nullable
• transmission string nullable
• has_keys boolean nullable
• odometer number nullable
• odometer_status string nullable
• condition string nullable
• condition_code string nullable
• primary_damage string nullable
• primary_damage_code string nullable
• secondary_damage string nullable
• title_type string nullable
• title_group string nullable
• title_group_code string nullable
• title_state string nullable
• actual_cash_value number nullable
• estimated_repair_cost number nullable
• currency string nullable
• current_bid number nullable
• high_bid number nullable
• buy_it_now_price number nullable
• sale_status string nullable
• sale_status_label string nullable
• bid_status string nullable
• has_bid boolean nullable
• is_sold boolean nullable
• is_seller_reserve_met boolean nullable
• is_sealed_bid boolean nullable
• sale_name string nullable
• auction_at integer nullable
• auction_time string nullable
• time_zone string nullable
• iana_time_zone string nullable
• updated_at integer nullable
• yard_name string nullable
• yard_number integer nullable
• physical_yard_number integer nullable
• city string nullable
• state string nullable
• country string nullable
• postal_code string nullable
• latitude number nullable
• longitude number nullable
• brand string nullable
• site_codes array (default: [])
• highlights array (default: [])
• report_providers array (default: [])
• image string nullable
• autocheck_score integer nullable
• autocheck_score_range string nullable
• autocheck_owner_count integer nullable
• autocheck_accident_record string nullable
• autocheck_odometer_record string nullable
• damages array (default: [])
  • @type string (default: "CopartLotDamage")
  • area string nullable
  • item string nullable
  • damage string nullable
  • severity string nullable
  • image string nullable
  • thumbnail string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No lot with this number is listed on Copart Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.