About The Car Selector API
Our Car Selector API allows a user to reach a vehicle derivative through selecting the manufacturer, range and model.
Progressive selection of the manufacturer, range and model also provides the vehicle's CAP-HPI CAPID.
The CAPID code can then be used to access all the background data on a car including prices, equipment, options, technical specifications, warranty and residual value/maintenance costs forecasts.
Dataset
The data is provided as an XML dataset, but you can change the type of data returned in your HTTPS request. Just swap 'json' for 'xml' in the 'd_Type' element of the request string to see a JSON dataset. JSON is the default type for the dataset if no 'd_Type' is set.
Our Demo
To select a vehicle just choose a manufacturer, then a range and model from the list boxes below.
We'll display the relative HTTPS {GET} requests for each stage of the selection and you can copy and paste the sample request strings into a browser address bar to see the raw XML data returned for the request (right click on the browser page displayed and you will see the XML dataset).
As each vehicle model selection is made the returned dataset includes the vehicle derivative's CAP-HPI ID code ('CAPID'), manufacturer, range and model name for verification.
{GET} Requirements
The actual {GET} request for each stage of the vehicle selection requires our standard security login/session token and progressive user choices for manufacturer, range and model.
Just choose a manufacturer from the selection box below and we'll display the HTTPS {GET} requests for manufacturers, model ranges and models.
You can copy and paste any of the sample request strings into a browser address bar to see the raw XML data returned for the request (right click on the browser page displayed and you will see the XML dataset).
You can also change the type of data returned in your sample request. Just swap 'json' for 'xml' in the 'd_Type' element of the request string to see a JSON dataset.
Security
A session token is created on initial login and must be included as a cookie with all HTTPS requests or the request will fail.
If the user's browser does not allow functional cookies then the {GET} request will become orphaned and the request cannot be linked to any other requests in the same session.
If the session token is not included then the session will be terminated, any data created in the session may be erased at the server and the user may need to re-authenticate with a new session.
For security reasons the HTTPS protocol must be used for all {GET} requests so that all data passed between the browser and the server is encrypted, including the session token.
Pair:Value Summary
d_type: xml or json for the required return data type (json if not specified)
manufacturer: a valid CAP-HPI manufacturer name
range: a valid CAP-HPI descriptor
model: a vald CAP-HPI descriptor