This article outlines the schema for inventory being sent to the BuyerBridge platform and is intended as a guide for new feed providers who wish to integrate with us.
The platform will ingest inventory in any of the below formats. The most common format used is a CSV file.
BuyerBridge supports HTTP or FTP for all formats above. If FTP is the preferred transfer mechanism BuyerBridge is setup to either retrieve the data from an FTP server or, more commonly, accept remote FTP uploads. New providers should indicate which protocol and configuration they prefer.
If the provider would like to send BuyerBridge their inventory via FTP we will supply connection details upon request.
Remote Dealer Identifiers (RDIs)
BuyerBridge uses RDIs to isolate a dealer's inventory within a feed provider as a whole. For each format, the platform supports one master file with string IDs within it or separate files entirely. It is up to the feed provider to determine which format fits their use case.
The schema for a vehicle can be found below. Fields with an * are required to ingest a vehicle.
|DealerId*||String||This value is not required if using file-based RDIs|
|Vin*||String||Non-standard VINs will be converted to 17 character strings for Marketplace|
|VehicleType||String||Car/Truck, Boat, Motorcycle, RV/Camper, Powersport, Trailer, Commercial or Other||If not provided we will default to Car/Truck|
|Certified||Boolean||TRUE or FALSE|
|NewUsed*||String||New or Used|
|Year*||Integer||4 Digits||Example: 2014|
|Body||String||Truck, Sedan, SUV, Coupe, Hatchback, Convertible, Wagon, Van|
|Transmission||String||Example: Automatic or Manual|
|PhotoUrlList*||String||A list of image URLs separated by commas ',' or pipes '|'|
|DetailsUrl*||String||Link to vehicle's details page|