Skip to content
English
Visit CLASSIC.COM
  • There are no suggestions because the search field is empty.

Auction Data Specifications

How to provide your auction listing data to CLASSIC.COM 

Thanks for your interest in including your listings on CLASSIC.COM! If you represent an auction house that sells classic, exotic, or specialty cars, please fill out this form to express interest.

We require that all sources be available in English and provide both upcoming and historical listings with up-to-date, accurate, factual, public information, including but not limited to:

  • Year, Make, and Model
  • VIN, or Chassis/Series if older than 1981
  • Location at time of sale
  • Status: For Sale, Sold, Not Sold, Withdrawn
  • Price: Sold price or Highest Bid (if Reserve was not met)
  • Images
  • Odometer
  • Text description


We reserve the right to approve or deny any inclusion requests at our own discretion, and remove data sources and/or listings that lack transparency, are misleading, outdated, or used as "click bait" to attract leads for other vehicles or purposes.

Once you are an approved Auction Partner, we typically receive auction data via API, JSON or XML data feed. However, we can also receive data via CSV upload. All data integration options are outlined below. 

It is your responsibility to ensure that the data is updated and accurate – including the required fields of VIN for every listing and final sale price (or highest bid if applicable) for all listings provided post-auction.

Steps to Auction Data integration:

  1. Sign a Partner Agreement. Provide your information here to get started.
  2. Share your test file or endpoint URLs. Choose from the options outlined below, and contact partnersupport@classic.com with any questions.
  3. Testing. We will work together to test the data and ensure it works properly.
  4. Go live! Your inventory will begin appearing on CLASSIC.COM.

Which integration method is right for you?

CLASSIC.COM supports three ways to get your auction inventory onto the platform:

  • Direct Integration: We typically receive auction data via API, JSON or XML data feed. This is the quickest and most accurate method, but it does require a developer to build and maintain the connection. View API Specifications here

  • FTP Feed: If an API is not available for your data, you can push a regularly updated CSV file to our FTP server. This doesn't require building an API, but it does need to be set up and automated on your end. You'll find more information on this alternative below.

  • Manual Submission: If you have limited technical capabilities, you can email us a CSV file to import manually. This option is only available for one-time, event-based auctions. If you run auctions on an ongoing schedule, you'll need to use one of the two options above.

API Specifications

We prefer to have a direct connection to your API in order to have the most accurate and up-to-date information. 

View API Specifications here

 

CSV File (via FTP)

If building an API isn't feasible for you, you can provide a CSV file.

The CSV can be uploaded to our FTP server via the credentials provided to you during onboarding. You will need an FTP server such as Filezilla. 

Download CSV Template here

All fields must follow specifications described in the Full Field Reference section below.

The filename should follow this format: <auction_name>_<auction_end_date_YYYYMMDD>.csv 

For example: yourauction_20260720.csv

 

CSV File (Manual submission)

If you do not have access to FTP upload and your auction is a one-time event, we can upload your CSV manually. 

Download CSV Template here

All fields must follow specifications described in the Full Field Reference section below.

The filename should follow this format: <auction_name>_<auction_end_date_YYYYMMDD>.csv

For example: yourauction_20260720.csv

Note: Your file will need to be provided at least twice:

  • Before the auction with the full listing information,
  • After the auction, updated with full price results.

 

Full Field Reference

All integration methods use the same underlying data model. The table below documents every supported field, whether it is required, and which format is expected. For API integrations, we can map your field names to ours with your assistance to identify the proper fields.

Field Type Required Description & Notes
uid String / Number YES

Unique identifier for the listing.

Must be unique across all listings for a given vehicle, even if re-listed.
lot_id String / Number No User-friendly ID; can match the lot number shown on your site.
vin String YES

Vehicle identification number

For vehicle older than 1981, this should be a 17-digit VIN.

Pre-1981 vehicles may use Chassis, Frame, or Series number instead.
title String YES*

Full listing title

ex: "1996 Porsche 911 Turbo"

*Required if year/make/model are not provided.
year Integer No*

4-digit model year.

*Required if title is not provided.
make String YES*

Manufacturer name.

*Required if title is not provided.
model String YES*

Model name.

*Required if title is not provided.

submodel		 String No

Sub-model

ex: "Turbo", "Targa"
trim String No Trim level
body_style String No

Body style

ex: "Coupe", "Sedan", "Convertible"
odometer Integer YES

Displayed odometer reading (numbers only)

Do not use commas, numbers only.

odometer_unit

 String YES

The unit of measurement used for the Odometer reading provided

mi or km
total_mileage_unknown Boolean No

Is the mileage entered know to be true, original miles?

TRUE or FALSE
exterior_color String No

Exterior color name

ex: "Red"
interior_color String No

Interior color name

ex: "Brown leather"
doors Integer No Number of doors
engine String No

Short engine description

ex: "5.0L V8" or "3.6L Flat 6 Turbo"
transmission_type String No Automatic or Manual
description String YES Full listing description text.
options String No Factory or aftermarket options. Comma-separated.
url String YES Direct link to the listing on your website.
country String YES

Country where the car is located

Please use the two-letter country code
city String YES*

City

*Required unless a combined location string is provided (API only).
state String YES*

State (US listings)

*Required unless location is provided.
zipcode String No Zip code (US listings)
main_image String (URL) YES

URL to access the primary listing image

Recommended Resolution: 2400 x 1800 px

No banners or watermarks
images List of URLs YES

URLs to access all additional images

If using API, send as array

If using CSV, send as comma-separated

Recommended Resolution: 2400 x 1800 px
status String YES

The status of the listing

Must be one of the following:

AVAILABLE
SOLD
NOT_SOLD
WITHDRAWN
lot_date String YES

The date this lot will sell at auction.

If the auction happens in multiple days, please be sure the lot date is correct for every entry.

If using API, send as YYYY-MM-DD

IF using CSV, send as MM/DD/YYYY
price Integer YES

Final price result must be provided after the auction.

If status is SOLD, input the final sale price

If status is NOT_SOLD, input the highest final bid.

Do not use commas, numbers only.
currency String YES

Currency that the price is entered in, using the ISO 4217 currency code:

ex: USD, CAD, EUR, GBP, etc.

 

For questions, contact our Partner Support team at partnersupport@classic.com