AutoFeed/Vehicle data integration
Vehicle data where the customer needs it
Connect a vehicle-data provider to your website or application, then put the returned information to work in the journey your customer is already taking.
A registration or VIN can save the customer from entering details you can retrieve.
AutoFeed integrates established vehicle-data providers into automotive websites and software. The useful result is not just a response from an API. It is a clearer enquiry, a better populated listing, a relevant product journey or a valuation process that begins with the right vehicle.
We work with the provider and market appropriate to the project. Available fields, permitted uses and lookup coverage vary by provider, country and vehicle.
01 In-page example
From a registration to a useful next step
Try the example registration. The vehicle record appears, then its available details carry into a trade-in enquiry. The customer can add the information that needs a human answer.
01 / Identify
02 / Vehicle record
2012 Volkswagen Golf
- Make
- Volkswagen
- Model
- Golf
- Variant
- Comfortline
- Year
- 2012
- Engine
- 1,598 cc
- Fuel
- Diesel
- Transmission
- Manual
- Body
- 5-door hatchback
03 / Continue the journey
Trade-in enquiry
Vehicle details already carried through
The customer can now add current mileage, condition, photographs and contact details. A valuation or offer would need the appropriate data and business process.
02 Applications
One lookup, several useful journeys
The data should serve a specific customer or business task. These are common ways to apply it:
- Vehicle enquiry and trade-in
- Start with a registration or VIN, then carry available vehicle details into the enquiry. The customer adds the condition, mileage and contact information the data source cannot know.
- Vehicle listings and product pages
- Use supplied identity and specification fields to help populate a listing or explain a vehicle. The source data and the seller’s own description remain distinct.
- Valuation and decision tools
- Bring licensed valuation data into a journey where it is useful, alongside the information needed to interpret it, such as mileage and condition.
- Parts and service journeys
- Identify the vehicle before showing relevant products or service options. Compatibility still depends on the quality and scope of the underlying data.
03 Integration
Build around the source and the destination
A project starts with the fields and rights available from the chosen provider, then the website or application that will use them. AutoFeed handles the connection, maps the returned fields into the customer journey and accounts for missing or uncertain values.
Depending on the market and provider, the input may be a registration, VIN or chassis number. The response may include identity, specifications, history, risk or valuation information. Those categories are not interchangeable, and a basic identity lookup does not establish a vehicle’s history or value.
Provider credentials stay server-side. The public interface receives only the information needed for its task, with the presentation and data handling shaped by the provider’s licence and the project requirements.
04 Markets
Choose data for the market, then design the experience
AutoFeed can work with an existing provider relationship or help identify a suitable source. Cartell is an example in Ireland and InfoAgent in Australia. UK and other markets require their own coverage and access assessment.
We establish which vehicles are covered, what each response contains, how often the data changes, permitted display and storage, lookup costs and the behaviour when no match is returned. Then we design the journey around what can actually be supplied.
Related
Publishing a dealer’s existing inventory is a different job. See vehicle stock integration.
Where should vehicle data enter your product?
Tell us about the website or application, the market, the provider if you have one, and the decision the data needs to support.