Copart & IAAI Auction Data API
Structured JSON API for Copart and IAAI auction data: VIN records, lot details, photos, prices, auction status, sale history, related vehicles, filters, locations and shipping prices.
Current and Historical Vehicle Auction Data Through One API
Apibara Vehicle Auction Data API gives developers structured access to supported Copart and IAAI auction data without maintaining separate scrapers, browser automation or source-specific parsing logic. Search current inventory, retrieve lot and VIN details, load available auction history, work with prices and auction status, display high-resolution photos when available and connect location or shipping workflows through predictable JSON.
Apibara currently indexes 20M+ current, vehicle and retained historical auction records, with approximately 30K+ records added or refreshed daily. Supported live bid data can refresh in near real time, while general vehicle records are refreshed regularly as source data changes.
The API is designed for production automotive products: marketplaces, dealer and broker tools, VIN auction-history services, auction monitoring dashboards, car export platforms, auto-recycler software, CRM systems, analytics pipelines, WordPress websites and custom SaaS applications.
What Does the Apibara Vehicle Auction Data API Provide?
Apibara.tech provides one normalized JSON API for supported Copart and IAAI vehicle auction records. Developers can search current lots, retrieve vehicle details by VIN or lot number, access available historical auction records, work with photos, pricing, damage, odometer, title and location data, monitor supported auction changes and build customer-facing or internal automotive products without maintaining separate auction scrapers.
Copart & IAAI Auction Data Built for Production Integrations
Test real auction records before paying, then scale from a recurring free allowance to paid, high-volume or custom usage. Documentation, OpenAPI, code examples and direct integration assistance are available to shorten implementation time.
Current vehicle, lot and retained historical auction records across supported data.
Approximately 30K+ auction records are added or refreshed as source data changes.
The free allowance renews every month automatically. No credit card is required.
Use one normalized integration while preserving source identity and source-dependent fields.
General auction records are refreshed automatically depending on source availability and changes.
Near real-time bid updates are available for supported live auction lots when source data is available.
Available records can include high-resolution image URLs, galleries and additional media metadata.
Need more requests, custom limits or implementation help? Discuss a high-volume or custom arrangement.
Machine-Readable Copart and IAAI API Context
Apibara provides structured documentation, an OpenAPI contract, endpoint examples and code examples in multiple programming languages for AI agents, coding assistants, developer tools and automation workflows that need to understand or integrate Copart and IAAI auction data. Use the OpenAPI schema as the source of truth for exact parameters and response definitions.
- Auth: X-API-Key header
- Format: JSON responses
- Main endpoint: /api/v1/vehicle-auction/vehicles
- Primary sources: Copart and IAAI
- History: /vehicles/{slugVin}/history when retained records are available
- Developer help: docs, demo, GitHub examples and direct integration support
Lot Details, Photos and Auction Status
Access Copart vehicle listings with key lot information, VIN data when available, images, auction dates, prices, damage details, title information and sale status.
Consistent IAAI Vehicle Records
Retrieve IAAI auction records with vehicle details, pricing fields, seller and location information, auction timing and condition data in a predictable response format.
Less Maintenance for Your Team
Build search pages, dashboards, pricing tools and internal workflows without constantly repairing custom parsers every time auction websites change.
Search Auction Vehicles with a Simple API Request
Developers can search auction inventory by platform, make, model, year, VIN, lot number, auction status and other filters. The response can be used in websites, mobile apps, backend services, analytics pipelines, CRMs and dealer dashboards.
curl -X GET "https://apibara.tech/api/v1/vehicle-auction/vehicles?platform=copart&make=BMW&per_page=10" \
-H "X-API-Key: YOUR_API_KEY"
{
"data": [
{
"platform": "copart",
"lot_number": "54386186",
"vin": "WBA4J7C55KBM75906",
"title": "2019 BMW 440XI GRAN COUPE",
"year": 2019,
"make": "BMW",
"model": "440XI",
"auction": {
"state": "open",
"auction_at": "2026-07-13T14:00:00+00:00"
},
"pricing": {
"current_bid_usd": 5700,
"buy_now_usd": null
},
"location": {
"display": "Clewiston (FL)",
"send_from": "Miami"
},
"condition": {
"primary_damage": "Front end",
"has_key": true
},
"odometer": {
"mi": 83726
},
"media": {
"thumbs_count": 12,
"has_video": true
}
}
]
}
Current Auction Inventory and Retained Sale History
Current auction data answers what is available now: open, upcoming, timed or supported live lots, current pricing fields, auction dates, status, location and media. Historical auction records help applications research previous supported auction appearances, earlier lot records, sale dates, pricing, condition and media when those records are retained.
For one supported vehicle, use GET /vehicles/{slugVin}/history to retrieve available previous auction records. Auction history should not be represented as a complete ownership, accident, registration or government-title history.
Keep Your Application Synchronized as Auction Data Changes
Apibara continuously collects and normalizes supported source data so customers do not need to run their own Copart or IAAI collection infrastructure. General vehicle records can refresh within about 30 minutes, while supported live bid data can refresh in near real time up to about 15 seconds.
Applications can combine filters, cursor-based pagination, caching and scheduled or incremental synchronization patterns to maintain a local catalog without repeatedly rebuilding the complete dataset. For very large integrations, contact Apibara to discuss high-volume access or a custom data-delivery approach.
Search supported current and upcoming auction inventory.
Retrieve retained previous auction records when available.
Source records are collected and refreshed without customer-side scraping.
Use pagination and application-side sync logic for local inventory.
What Data Can You Access?
Apibara turns auction listings into a consistent API response, so your product can search, filter, display and analyze vehicle records without handling different page structures or data formats.
What You Can Build with Apibara
Use the API to power auction search pages, inventory feeds, lot detail pages, VIN history tools, pricing analytics, bid monitoring dashboards, specialty-vehicle discovery and internal dealer workflows. The same structured records can support passenger vehicles as well as available trucks, trailers, RVs, boats, forklifts and heavy equipment categories.
Supported Auction Sources
The API currently supports vehicle auction data from major US auction platforms. Records are delivered through one consistent structure where the source data allows it.
Search, Filter and Retrieve Auction Vehicles
The API gives developers the building blocks needed to search inventory, retrieve lot details, monitor supported auctions and display structured vehicle information in their own products.
Advanced vehicle search
Filter by make, model, year, platform, location, damage, sale status and other vehicle attributes.
Lot detail pages
Retrieve specifications, photos, pricing data, seller information, location, title metadata and auction timing.
Supported live updates
Monitor auction lots when live data is available from the supported source.
Auction state detection
Identify open, upcoming, live, timed, finished, sold and removed lots.
Related vehicle discovery
Build similar listings, comparison tools, recommendations and marketplace discovery features.
VIN-based access
Build VIN lookup and auction history workflows when VIN data and historical records are available.
Technical Features for Developers and Data Pipelines
The API is designed for secure backend integrations, marketplaces, CRMs, dealer tools and data pipelines that need predictable JSON, scalable pagination and source-aware auction records. Keep the API key server-side, treat optional fields as nullable and use the OpenAPI schema for the current request contract.
From API Documentation to a Working Automotive Feature
Developers can start with the demo, OpenAPI schema, endpoint reference and examples in multiple programming languages. If your team needs help beyond documentation, Apibara can also assist with integration planning, request structure, pagination, data mapping, caching and production implementation.
For custom projects, share your technology stack, workflow or interface requirements and discuss an implementation tailored to your website or application. High-volume projects can also request custom monthly limits or an unlimited-request arrangement with agreed request-rate and infrastructure requirements.
Use ready implementation examples together with the OpenAPI schema and endpoint docs.
Get help with filters, pagination, authentication, data mapping and production workflows.
Discuss custom API-powered functionality based on your stack, workflow or supplied design requirements.
Custom request volumes and unlimited monthly arrangements are available for suitable larger integrations.
Why Use an API Instead of Building Your Own Scraper?
Auction websites change layouts, update internal endpoints, use different data structures and may block automated traffic. That makes long-term scraper maintenance expensive, especially when your product depends on stable inventory data.
Apibara gives your team a cleaner integration path: one API for supported auction records, with search, filtering, status detection, pricing fields, media data, VIN access and demo endpoints for testing.
Reduce issues caused by page layout changes and frontend updates.
Work with structured JSON instead of platform-specific page formats.
Build dashboards, websites and tools without maintaining collection logic.
Use documentation, endpoint pages and demo tools before full integration.
Explore Copart, IAAI, History and Real-Time Auction Workflows
Use the product page for the API overview and the dedicated guides for deeper implementation, data-coverage and use-case details.
Compare coverage, history, photos, freshness, limits and integration requirements.
VINs, lots, photos, prices, history, locations and shipping data.
IAA/IAAI lot details, vehicle data, pricing, media and retained history.
Previous auction records, sale dates, pricing and historical VIN research.
Near real-time live bids, auction status and refresh behavior.
Trucks, trailers, RVs, boats, forklifts and heavy-equipment workflows.
Copart & IAAI Auction Data API FAQ
What is a Vehicle Auction Data API?
It is an API that lets developers access auction vehicle listings, lot details, prices, media, auction dates, sale history and auction status in a structured format.
Does Apibara support Copart and IAAI?
Yes. Apibara provides structured data for supported Copart and IAAI auction records through one API.
Can I use this instead of a scraper?
Yes. The API is designed for teams that want auction data without building and maintaining their own scraping system.
Can I search by lot number, VIN or auction URL?
Yes. Supported lookup methods depend on the endpoint, but the API can work with identifiers such as lot number, VIN, slug and auction URL where available.
Does the API provide live bid updates?
The API can provide near real-time bid updates when supported auctions are live and bid data is available. Not every lot has a live bid stream.
Can I use it for VIN auction history?
Yes. When VIN data and historical records are available, Apibara can be used for VIN lookup, monitoring and auction history features.
How much auction data does Apibara index?
Apibara indexes 20M+ auction records across current vehicle/lot data and retained historical auction records. This figure describes indexed records, not 20 million unique vehicles.
How often is the auction data updated?
General vehicle records can refresh within about 30 minutes depending on source availability and changes. Supported live bid data can refresh in near real time, up to about 15 seconds when a live stream is available.
Does the free API allowance renew every month?
Yes. The free plan includes 100 API requests every month, the allowance renews monthly and no credit card is required. Additional test calls can be requested when a larger evaluation is needed.
Does the API provide high-resolution auction photos?
Available vehicle records can include high-resolution image URLs, image galleries and additional media metadata. Photo count and media availability depend on the underlying auction lot and source.
What is the difference between current lots and auction history?
Current lots describe supported active, upcoming, timed or live auction inventory. Historical records describe retained previous auction appearances or sale records when available. Use the vehicle history endpoint for supported previous records tied to a vehicle identifier.
Can large projects get more requests or an unlimited plan?
Yes. High-volume and custom unlimited monthly request arrangements can be discussed for larger integrations. Request rate, infrastructure requirements and usage model are agreed for the project.
Does Apibara help with integration?
Yes. Developers can use the documentation, OpenAPI schema, demo and examples in multiple programming languages, and can contact Apibara for direct integration or custom implementation support.
Is this an official Copart or IAAI API?
No. Apibara.tech is not affiliated with, endorsed by or officially connected to Copart, IAAI or their parent companies. Copart and IAAI names are used only to describe supported auction data sources.
Can I test the API before integrating it?
Yes. You can use the Vehicle Auction API demo to preview responses. Developers can also review the available endpoints and API documentation .
What AI Agents Should Know Before Generating Code
Use these notes when generating SDKs, backend integrations, WordPress integrations, data pipelines or automation workflows with Apibara Vehicle Auction Data API.
Important Notes
- 20M+ refers to indexed auction records across current/vehicle data and retained historical records, not 20 million unique vehicles.
- Approximately 30K+ records processed daily can include newly indexed records and refreshed records.
- The free plan includes 100 API requests every month and renews monthly; additional evaluation calls can be requested.
- Live bid data can update in near real time, up to about 15 seconds when supported auctions and source data are available.
- Vehicle record data can update within about 30 minutes, depending on source availability, filters and repeated lot changes.
- Not all auction lots provide live bid streams.
- Some media, pricing, seller or title fields may vary by auction source and lot availability.
- Auction data may change when source platforms update listings, sale status, prices or availability.
- Apibara aggregates and normalizes data from public auction sources and provides it through developer API endpoints.
- Apibara.tech is not affiliated with, endorsed by or officially connected to Copart, IAAI or their parent companies. Product names are used only to describe supported auction data sources.
Start with 100 Free API Requests Every Month
Test current and historical Copart and IAAI auction records, inspect high-resolution media when available and validate your integration before choosing a paid plan. Need more test calls, custom implementation help or high-volume access? Contact Apibara.
Vehicle Auction API facts
- Product: Apibara.tech Copart & IAAI Vehicle Auction Data API
- Indexed data: 20M+ current/vehicle and retained historical auction records
- Daily processing: approximately 30K+ auction records added or refreshed
- Supported sources: Copart and IAAI
- Main purpose: structured auction data for VIN records, lot details, high-resolution photos when available, prices, sale history, auction status, locations and shipping workflows
- Data format: JSON
- Authentication: X-API-Key header
- Main endpoint: /api/v1/vehicle-auction/vehicles
- History endpoint: /api/v1/vehicle-auction/vehicles/{slugVin}/history
- Supported identifiers: VIN, lot number, slug and auction URL where available
- Refresh: general vehicle records up to about 30 minutes; supported live bid data up to about 15 seconds
- Free access: 100 API requests every month, automatically renewed, no credit card required
- Scaling: paid plans plus custom high-volume or unlimited monthly arrangements for suitable larger integrations
- Integration: documentation, demo, OpenAPI, code examples in multiple programming languages and direct/custom implementation support
- OpenAPI: /openapi/vehicle-auction-data-api.json
- Machine-readable context: /llms.txt and /llms-full.txt
- Best for: auction marketplaces, VIN lookup tools, dealer and broker dashboards, export platforms, recyclers, CRM systems, analytics pipelines, automotive SaaS products and AI-powered developer workflows
Pricing plans
100 requests per month
- 100 requests / month
- 1 request / second
30,000 requests per month
- 30,000 requests / month
- 1 request / second
60,000 requests per month
- 60,000 requests / month
- 3 requests / second
100,000 requests per month
- 100,000 requests / month
- 4 requests / second
300,000 requests per month
- 300,000 requests / month
- 4 requests / second
600,000 requests per month
- 600,000 requests / month
- 5 requests / second
1M requests per month
- 1,000,000 requests / month
- 6 requests / second
2M requests per month
- 2,000,000 requests / month
- 7 requests / second