Adding Auction Inventory on CLASSIC.COM
A complete guide to connecting your auction listings to the CLASSIC.COM platform.
Which integration method is right for you?
CLASSIC.COM supports three ways to get your auction inventory onto the platform. Use the descriptions below to figure out which one fits how your auctions work.
-
API Integration: This is best if you run ongoing auctions or have live inventory that changes frequently. It requires a developer to build and maintain the connection. Your platform exposes endpoints that we query directly. You can find more details on API integration in this link.
-
CSV Feed via FTP: You push a regularly updated CSV file to our FTP server, and we handle the rest. This is a good middle-ground option. It 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: You send us a spreadsheet-like file in CSV file for each event, and we import it. This option is only available for sporadic, event-based auctions. If you run auctions on an ongoing or regular schedule, you'll need to use one of the two options above.
CSV Feed via FTP
If building an API isn't feasible, you can push a regularly updated CSV file directly to CLASSIC.COM's FTP server. We will provide you with credentials during onboarding and handle ingestion automatically on our end.
CSV File Naming Convention
Your CSV file name should follow this format, and dates in the file name should use the format YYYYMMDD.
<auction_name>_<auction_end_date>.csv
Example: classic_example_auction_20250720.csv
The CSV must follow the field names and formats in the Full Field Reference section below.
Dates within this CSV file will use the MM/DD/YYYY format.
Manual CSV Submission (event-based auctions only)
For sporadic, event-based auctions that don't run on a regular schedule, CLASSIC.COM accepts one-time CSV file submissions per event. You send us the file, and we handle the import.
Eligibility: This option is only available for auctions that run infrequently. Ongoing or regularly scheduled auctions must use the API or feed connection methods above.
Files must follow the same CSV format and field naming conventions described in the Full Field Reference section below. Send your file to your CLASSIC.COM contact ahead of the auction date to allow time for review and ingestion.
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.
If any field names in your system don't match those listed below, that's fine! Let us know your field names, and we'll handle the mapping on our end.
| 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 | 17-digit VIN. Pre-1981 vehicles may use a chassis number instead. |
| title | String | YES* | Full listing title (e.g., "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 (e.g., "Turbo", "Targa"). |
| trim | String | No | Trim level. |
| body_style | String | No | E.g., "Coupe", "Sedan", "Convertible". |
| odometer | Integer | YES | Displayed odometer reading (numbers only). |
| odometer_unit | String | YES | mi or km |
| total_mileage_unknown | Boolean | No | true or false |
| exterior_color | String | No | Exterior color name. |
| interior_color | String | No | Interior color name. |
| doors | Integer | No | Number of doors. |
| engine | String | No | Short engine description, e.g., "5.0L V8" or "3.6L Flat 6 Turbo". |
| transmission_type | String | No | Automatic or Manual |
| description | String | YES | Full listing description. |
| options | String | No | Factory or aftermarket options. Comma-separated. |
| url | String | YES | Direct link to the listing on your site. |
| country | String | YES | Country where the car is located. |
| 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 | Primary listing image. No banners or watermarks. Recommended: 2400 x 1800 px. |
| images | List of URLs | YES | All additional images. Comma-separated in CSV; array in API. Same resolution recommendation. |
| status | String | YES | One of: AVAILABLE, SOLD, NOT_SOLD, HIGH_BID, WITHDRAWN |
| lot_date | String | YES | Auction end date. Format: YYYY-MM-DD (API) or MM/DD/YYYY (CSV). |
| price | Integer | YES | Final sale price if SOLD, or final bid if HIGH_BID or NOT_SOLD. |
| currency | String | YES | ISO 4217 currency code: USD, CAD, EUR, GBP, etc. |
Overview: How to Start Adding Auction Inventory
Once you've reviewed the integration options above, reach out to your CLASSIC.COM contact to begin onboarding. Here's what to expect:
- Choose your integration method - API, FTP feed, or (if eligible) manual CSV.
- Share your endpoint URLs or a sample CSV so we can review field mapping.
- Receive your API key (if using API integration), and complete a test data exchange.
- Go live! Your inventory will begin appearing on CLASSIC.COM.
For questions, contact your CLASSIC.COM account representative or email partnersupport@classic.com