Vehicle Auction API for Auto Recyclers & Salvage Yards

Why Auto Recyclers Need Auction Data

For a retail buyer, an auction vehicle is often evaluated as a complete car. An auto recycler looks at the same record differently. A vehicle with severe body damage may still contain a valuable engine, transmission, doors, electronics, wheels, interior components or body panels. A cosmetically cleaner vehicle may be a poor donor if its primary damage affects the high-value assembly the yard needs.

The sourcing question is therefore not simply “Is this a good vehicle?” It is closer to:

• Does the year, make, model and configuration match current demand?
• Is the likely damage away from the components the yard intends to recover?
• Does the vehicle have keys, useful photos and a reported run condition?
• Is the current bid still compatible with expected recovery value?
• How far is the auction facility from the yard or preferred transport route?
• Has this VIN appeared at auction before, and what information is available from earlier records?

A structured salvage auction API makes these questions searchable and repeatable. It does not replace an experienced buyer, inspection or fitment catalog. It gives the buyer a cleaner data pipeline and a faster way to create a shortlist.

What Data Is Useful for Donor Vehicle Sourcing?

No single field proves that a component is usable. Damage descriptions are source data, photos do not reveal every defect, and “runs and drives” is not a mechanical warranty. The safest workflow combines auction data with human review, interchange data, inventory demand and a yard-specific valuation model.

Auto Recycler API Endpoint Map

All paths use the base URL https://apibara.tech/api/v1/vehicle-auction and authenticate with the X-API-Key header. Use the live endpoint reference as the current contract for parameters and response fields.

How to Search for Potential Donor Vehicles

The search endpoint accepts both Copart and IAAI inventory. A recycler can combine filters to reduce a large auction feed to a manageable buying queue. This example looks for newer hail-damaged Toyota vehicles with keys at supported Florida auction locations:

curl -G "https://apibara.tech/api/v1/vehicle-auction/vehicles" \
  -H "Accept: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  --data-urlencode "make=TOYOTA" \
  --data-urlencode "year_from=2020" \
  --data-urlencode "damage[]=Hail" \
  --data-urlencode "has_key=With" \
  --data-urlencode "lot_sub_status=Open" \
  --data-urlencode "loc_state=FL" \
  --data-urlencode "per_page=20"

Do not assume that every literal filter value is permanent. Use GET /vehicles/filters to load currently supported makes, models, damage groups, run-condition values, price ranges and other metadata for your interface.

Useful filters for salvage-yard buyers

• platform — choose copart or iaai, or omit it for supported inventory across both sources;
• s — search by VIN, lot number or vehicle title;
• make, model, year_from and year_to — define the target vehicle family;
• damage[] and run_cond — screen condition-related candidates;
• has_key — distinguish supported records with and without reported keys;
• odometer_from and odometer_to — limit reported mileage;
• price_min and price_max — keep candidates inside an acquisition range;
• seller_type and sale-document filters — support business-specific review rules;
• loc_state, facility_id, zip and radius — control transport distance;
• auction_date_from, auction_date_to and today_only — build daily buyer queues.

Copart and IAAI in One Recycler Search

Many auto recyclers source from more than one auction platform. Maintaining separate response structures makes it harder to compare candidates, deduplicate VINs and build one buyer workflow. Apibara.tech keeps a normalized hierarchy for common data while preserving platform, platform_id and lot_number so the source is never lost.

This matters because normalization should not erase genuine differences. Auction statuses, damage labels, sale documents, media and available prices can vary by source and lot. Your database should store the normalized fields used by the product and retain the source identity needed for traceability.

For platform-specific integration details, see the guides to the Copart API for vehicle auction data and the IAAI API for auction lot details.

How to Inspect One Auction Vehicle

After a search result passes initial rules, retrieve the single-vehicle record by VIN, lot number or another supported public identifier:

curl "https://apibara.tech/api/v1/vehicle-auction/vehicles/WBA4J7C55KBM75906" \
  -H "Accept: application/json" \
  -H "X-API-Key: YOUR_API_KEY"

The detailed response can include identity, auction state, pricing, seller, facility, condition, odometer, vehicle specifications, sale document and media. A recycler dashboard can turn those groups into a review checklist:

1. Confirm the VIN, source platform and lot number.
2. Review the damage labels and every available image.
3. Compare engine, transmission, drive type and body information with a trusted fitment source.
4. Check odometer, keys, run condition and available seller information.
5. Review sale document and operational restrictions with qualified staff.
6. Add current bid, fees and transport to the acquisition estimate.
7. Record the decision, maximum bid and buyer notes in the internal system.

Auction Photos and Damage Screening

Photos are central to remote donor-vehicle review because the same primary damage label can describe very different physical outcomes. A buyer may use images to check the apparent impact area, missing components, water line, interior condition, deployed airbags, wheel damage and whether high-value assemblies are visibly present.

Image review still has limits. Auction photos may not show the underside, internal mechanical damage, storage damage or parts removed after photography. Photo count and quality vary, while video and 360-degree media are available only for supported listings. Treat images as evidence for triage, not as a substitute for inspection.

For galleries, store the media URLs returned by the vehicle record, use lazy loading and handle missing images gracefully. The supported image-proxy endpoint can be used only with eligible source image URLs returned by the API.

Using Auction History to Avoid Weak Buying Decisions

A current listing is only one snapshot. When available, auction history can show earlier records associated with the vehicle, including platform, date, price and sale status. That information can help a recycler notice a relisting, compare earlier photos or mileage, and investigate why a candidate returned to auction.

curl -G "https://apibara.tech/api/v1/vehicle-auction/vehicles/WBA4J7C55KBM75906/history" \
  -H "Accept: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  --data-urlencode "per_page=20"

History availability depends on the VIN, lot, platform and retained data. An empty history response does not prove that the vehicle has never appeared at auction. Auction records are also not a complete ownership, accident, repair or government-title report. Read the dedicated VIN Auction History API guide for appropriate uses and limitations.

Finding Comparable and Alternative Donor Vehicles

The related endpoint can return similar upcoming and past inventory for a resolved vehicle. In a recycler workflow, comparable records can serve three purposes:

• offer alternatives when the current bid exceeds the yard’s maximum;
• compare location, damage, mileage and pricing across similar vehicles;
• support a buyer’s estimate with more than one auction record.

curl "https://apibara.tech/api/v1/vehicle-auction/vehicles/WBA4J7C55KBM75906/related" \
  -H "Accept: application/json" \
  -H "X-API-Key: YOUR_API_KEY"

“Related” does not mean parts-compatible. Use it for inventory discovery and market comparison, then verify fitment using OEM numbers, a recognized interchange catalog or another authoritative parts-data source.

Location, Transport and Acquisition Cost

The winning bid is not the full landed cost. A recycler may also need to account for auction fees, loading, inland transport, storage, labor and processing. Location filters help keep buying activity inside a serviceable area before a candidate reaches manual review.

The locations endpoint supports platform, state, facility, text and ZIP-radius search. It can return facility identity, city, state, ZIP, coordinates, sale schedule and distance when available:

curl -G "https://apibara.tech/api/v1/vehicle-auction/locations" \
  -H "Accept: application/json" \
  -H "X-API-Key: YOUR_API_KEY" \
  --data-urlencode "state=FL" \
  --data-urlencode "zip=33166" \
  --data-urlencode "radius=100" \
  --data-urlencode "units=mi" \
  --data-urlencode "per_page=20"

Apibara.tech also exposes supported auction-to-port shipping prices for export workflows. Those prices are not a universal quote for delivery to every salvage yard. A domestic recycler should connect facility data to its own carrier rates or transport provider.

A Practical Donor Vehicle Scoring Model

The API returns source and normalized vehicle data; the recycler supplies the business logic. A simple internal score can help prioritize review without pretending to automate the final purchase decision.

Keep the score explainable. Buyers should be able to see which facts increased or decreased a candidate’s priority, open the source images and override the ranking when experience suggests a different result.

Recommended Integration Architecture

1. Call the API from a protected backend. Never expose X-API-Key in frontend JavaScript or a mobile application bundle.
2. Load current filter metadata. Cache it for the search interface and refresh it periodically.
3. Run saved acquisition searches. Use separate profiles for vehicle families, damage patterns, regions and budget limits.
4. Synchronize results with cursor pagination. Follow meta.next_cursor; do not construct cursor tokens manually.
5. Store source identity. Preserve VIN, platform, lot number and fetched timestamps for deduplication and traceability.
6. Retrieve full details on demand. Load the single-lot record, history and related data only when the workflow needs them.
7. Enrich with internal data. Combine auction records with demand, sales velocity, inventory, fitment and transport information.
8. Keep human approval. Let experienced buyers validate photos, parts relevance, documentation and maximum spend.
9. Monitor freshness, errors and usage. Use cached data during temporary failures and show when the record was last updated.

Data Freshness, Pagination and Errors

Supported live bid data may update approximately every 15 seconds, while general vehicle records may update within approximately 30 minutes. These intervals are approximate and are not guaranteed for every lot or auction. A buyer interface should display the latest successful fetch time and avoid describing cached data as live.

• Pagination: collection endpoints use cursor pagination with a maximum per_page value of 20.
• 401: the API key is missing or invalid.
• 404: the requested supported vehicle or resource was not found.
• 422: one or more request parameters failed validation.
• 429: the quota or rate limit has been reached; pause unnecessary requests and check usage.
• 5xx or timeout: retry safe reads with capped backoff and show timestamped cached data when appropriate.

Auction records can change when a lot is updated, rescheduled, sold, removed or finalized. Refresh active buying candidates more frequently than closed records, but do not generate unnecessary requests for vehicles no longer being considered.

What the API Does Not Decide

A reliable article and a reliable product should be explicit about the boundary between auction data and recycler expertise:

• It does not guarantee that a part fits another vehicle.
• It does not confirm hidden mechanical or structural condition.
• It does not guarantee the accuracy or completeness of every source field.
• It does not determine whether a document is acceptable for a specific jurisdiction or business process.
• It does not calculate auction fees, dismantling labor, storage cost or resale demand unless your application adds those inputs.
• It does not replace inspection, legal review, environmental compliance or an experienced buyer.

These limits do not reduce the value of an auto salvage inventory API. They clarify what it should do well: deliver consistent, searchable auction records so a recycling business can apply its own knowledge faster.

Frequently Asked Questions

What is a vehicle auction API for auto recyclers?

It is a developer interface that lets recycling software search auction inventory and retrieve structured vehicle, condition, pricing, media, location and history data. It can help a salvage yard identify potential donor vehicles and organize acquisition review.

Can the API search both Copart and IAAI vehicles?

Yes. Apibara.tech exposes supported Copart and IAAI inventory through one normalized API. Use platform=copart or platform=iaai for one source, or search supported inventory without a platform filter.

Can a salvage yard search by damage type?

Yes. The vehicle search endpoint supports normalized damage[] filters together with make, model, year, run condition, key availability, price, odometer and location filters. Load current supported values from /vehicles/filters.

Does the API identify compatible parts?

No. Auction records may include useful vehicle specifications, but final part interchange must be verified through OEM numbers, a trusted fitment catalog or another authoritative parts-data system.

Can I find one donor vehicle by VIN or lot number?

Yes. Search with the s parameter or retrieve a supported record directly through GET /vehicles/{slugVin} using its VIN, lot number or public identifier.

Does the API include auction photos?

Supported records can include thumbnails, larger photos, video and 360-degree media when available. Media count and quality vary by listing, and photos should not be treated as a complete inspection.

Can auto recyclers retrieve previous auction records?

The history endpoint returns available earlier auction and sale records for a supported vehicle. Coverage depends on the VIN, lot, source and retained data, so an empty response is not proof that no prior auction event exists.

Can I calculate the profitability of a donor vehicle with the API?

The API can supply inputs such as current bid, damage, odometer, location and related records. Profitability requires the recycler to add auction fees, transport, labor, inventory demand, expected part sales and its own risk assumptions.

How current is the auction data?

Supported live bid data may update approximately every 15 seconds and general vehicle data within approximately 30 minutes. These are approximate intervals rather than a guarantee for every record.

Is Apibara.tech an official Copart or IAAI integration?

No. Apibara.tech is an independent vehicle auction data provider and is not owned by or presented as an official partner of Copart or IAAI.