Introduction

This documentation is a comprehensive overview about the TecAlliance OneDB API. It is designed to help developer to request and exchange vehicle and part data with their internal IT system. You have to be a TecAlliance OneDB API customer in order to use this API and exchange data with your internal IT solution.

The OneDB API allows you to request vehicle data in various ways, e.g. VIN search, number search and via manufacturer > model > vehicle facet. All response follows the same standard and include all important information regarding your requested vehicle. OneDB provides you also part data for your automotive aftermarket needs. You can search for part number or OE number and get a comprehensive response back.

There are no specific programming languages and knowledge required to start using the API. The API is platform and language independent. Data transfer and exchange is done via RESTful/JSON.

You can find more information from below about how to use our API. If you want to try the search patterns from front-end, you may take a look at our China web catalog (free to use): www.tecalliance.cn.

Part 1. Find account authority: TecDoc API - Countries / Languages / Brands / Product groups / Manufacturer.

Part 2. If you want to find data on Ktype vehicle level (without information for sales version etc.), you may use below search patterns:

  1. VIN / Katashiki->Ktype->Part. VIN to kType (input VIN, output Ktype) / Katashiki to Ktype (input Katashiki, output Ktype) ->TecDoc API - Parts search request for specific vehicle (input Ktype ID, output linked parts). VIN to Ktype SEA, Katashiki to Ktype SEA are used for customers outside China.

  2. Ktype- >Part. TecDoc API - Vehicle search with carId filter (input Ktype ID, output Ktype) / TecDoc API -Vehicle search with engine code filter (input engine code, output Ktype ) / TecDoc API - Manufacturer, model, vehicle facet search (get Ktype via vehicle tree)->TecDoc API - Parts search request for specific vehicle (input Ktype ID, output linked parts).

  3. Part number->Part. TecDoc API - Parts search (all options) (input part number with articleNumber criteria / input uid with uid criteria, output part). uid can be found from other functions output.

  4. Multiple filters-> Part. TecDoc API - Parts search (all options) (input OE number with oemNumber criteria + input brand ID with dataSupplierIds criteria + input product group ID with productGroups criteria + input Ktype ID and vehicle type with carId and linkageTargetType criteria, output parts). You may use one or combined filters. Or you can use TecDoc API - OE number search (input OE number, output parts). Space is not counted for this function.

  5. Reference number->Part. TecDoc API - Parts search (all options) (input reference number with searchQuery criteria, output parts). D code belongs to trade number.

  6. Any number-> Part. TecDoc API - Multiple number search (fuzzy search) (input any number, output parts).

  7. Multiple part numbers-> Part. TecDoc API - Multiple part number search (input part numbers, output parts).

  8. Part-> Vehicle linkages. TecDoc API - Part linkage (input uid, output vehicle linkages).

Part 3. If you want to find data on ChinaID (ShortID) vehicle level (with information for sales version etc.), you may use below search patterns:

  1. VIN -> ChinaID -> Part. ChinaID API - VIN search (input VIN, output ChinaID )-> ChinaID API - Parts search (input shortId with shortId criteria, output linked parts).

  2. VIN -> OE -> Part. Extra (input VIN, output ShortID -> input ShortID, output product group -> input ShortID + product group, output OE -> input OE, output part).

  3. ChinaID -> Part. ChinaID API - Vehicle number search (input ShortID / ModelId / Ktype, output ChinaID) / ChinaID API - Manufacturer, model, vehicle facet search (get ChinaID via vehicle tree)-> ChinaID API - Parts search (input shortId with shortId criteria, output linked parts).

  4. Search parts from ChinaID. ChinaID API - Part number search - shortID > productgroups > brands > parts (input ShortID, output product group -> input ShortID + product group, output brand -> input ShortID + product group + brand, output part).

  5. Part number -> Part. ChinaID API - Parts search (input part number with articleNumber criteria / input uid with uid criteria, output part). uid can be found from other functions output.

  6. Multiple filters -> Part. ChinaID API - Parts search (input brandID with dataSupplierIds criteria + input product group with productGroups criteria + input ShortID with ShortID criteria, output part). You may use one or combined filters.

  7. Reference number -> Part. ChinaID API - Parts search (input reference number with searchQuery criteria, output part). D code belongs to trade number.

  8. Part -> Vehicle linkages. ChinaID API - Part linkage (input uid with uid criteria / input brand ID with dataSupplierId criteria / input article number with articleNumber criteria, output vehilce linkages).