Damage & Repair Cost Reports

Embed damage reports into hot lots, vehicle listings, auction feeds, or internal workflows. Give buyers and sales teams a damage signal before they request a quote, place a bid, or commit to import.

Produced in the Partsify platform. For high-value lots, final customer decisions, and vehicles where repair context can make or break the deal.

Served by the API. For hot lots, fresh arrivals, auction feeds, and importer websites where buyers need a quick condition signal at scale.

How the API works

• You send the lot itself: the auction source and lot number, the auction's https URL, the vehicle's VIN, make, model and year, and 1 to 30 photograph URLs. A Copart or IAAI feed already carries every one of those fields, so it needs no reshaping before it can be scored.
• The request is queued and answers immediately with a report identifier, because damage detection across a full photo set is not a request-response operation. Your system is called back when the report is ready, so a listing page never blocks waiting on it.
• The finished report comes back as a written damage summary, an estimated damage cost and the list of damaged categories, in English, Polish, Ukrainian or Russian. Asking for the same lot in the same language again returns the existing report instead of generating a second one.

What the response carries

• JSON: a status, a written damage summary, an estimated damage cost and the damaged categories for each lot.
• The API serves the Light report, a damage signal built for screening whole feeds. The full Pro report, with OEM part numbers, supplier prices and labor hours, is produced in the Partsify platform.
• Key-authenticated over HTTPS on a host of its own, separate from the web application, so an API incident and a site incident are never the same incident.
• Asynchronous by design: submit, take the identifier, receive the callback. Nothing in your listing render path waits on machine vision to finish.

Who it fits

Teams with inventory of their own — an importer's listing site, an auction aggregator, an internal bidding tool — who want the condition signal to appear where their users already are, instead of sending them to a third-party site in the middle of a decision.

It is the wrong tool for a handful of reports a month. The platform's web interface covers that with no integration work at all, and what the API is actually for is cost per lot at feed scale.

API reference

Two endpoints on api.partsify.io. Every request carries your API key as Authorization: Bearer <key>.

• POST /api/v1/generate_report_light Queues a Light damage report for one Copart or IAAI lot. Answers 202 with a task_id and a public_report_id.
• GET /api/v1/get_report/{public_id} Returns a finished report: the written summary, the estimated damage cost and the damaged categories.

What you send

source (copart or iaai), lot_number, auction (name and https URL), vehicle (VIN, make, model and year required; body style, mileage, title status, primary and secondary damage and key availability optional), images (1 to 30 https URLs) and an optional language: en, pl, uk or ru.

What comes back

status is processing, finished or failed. A finished report carries partsify_summary, damage_cost_estimation and damaged_categories. Errors come back as 400 for invalid input, 401 for a missing or invalid key, 403 when access is denied and 404 when the report is not ready yet or does not exist.

Webhook

When a report is ready, Partsify posts its report_id, task_id and status to the webhook URL set on your account, which is required before the first request. A delivery that does not get a 2xx answer is retried, up to five attempts, with the wait between them growing from a minute to a few hours.

Full schema and a live console: api.partsify.io/docs

Tell us what volume, sources, and workflow you need.

Share your auction sources, report volume, API needs, or website goals. We will route the request and follow up with the right next step.

Does Partsify inspect hidden structural damage?

No. A remote report cannot replace a physical teardown, and Partsify does not claim to detect hidden structural, frame or mechanical damage. It reads the auction photos for visible damage, then names the likely replacement parts with OEM numbers and current supplier prices, estimates labor hours, and totals the repair before you bid.

Partsify is operated by SCRAPEX LTD, Limassol, Cyprus. The interactive report tool requires JavaScript. Legal Information · Contact Us · Blog