Autodata API Developer Blog

This release contains the following new API and enhancements:

• Enhancement to available languages for Motorcycles APIs

Enhancement to available languages for Autodata Motorcycles API

The Motorcycle API responses were previously displayed in English by default for Greek and the Eastern European languages we support. However, we are happy to say that we are now able to return the API responses in the following translated languages:

Czech (cs-cz)

Croation (hr-hr)

Greek (el-gr)

Hungarian (hu-hu)

Russian (ru-ru)

This release contains the following new API and enhancements:

• Enhancement to Component Locations API (alpha)

Enhancement to Component Locations API (alpha)

Continuing on with the recent development in providing a more comprehensive data response from this API, we have introduced SRS content to the collection of subjects (Engine management, Air Conditioning, ABS, Electrical Component Locations, Fuse box and Relay Plates, and now SRS).

Like with the other subjects in the API, the response for the SRS subject will include hotspot coordinates for the components highlighted in the callout list and their related translated textual description allowing for the hover over feature.

This release contains the following new API and enhancements:

• Pin Data API (alpha)
• Enhancement to Component Locations API (alpha)

Pin Data API (alpha)

 This API provides information to support the testing of the control module pins on the terminal for a vehicle, such as images of terminals, component and circuit description, the ECM pin number, signal description and more.

This API has two call methods. The first call provides you with a list of variants for a given MID. The second call then provides you with the pin data for that given MID and variant, containing the Image of the control module and information on the components that the pins represent, as well as the expected electrical value.

Enhancement of Component Locations API (alpha)

 In addition to the recent enhancement to the Component Locations API regarding images, the API now also includes Fuse box / Relay Plate content, using the images API to support the callout lists that helps to identify the fuses present in the fuse box image.

The response will include hotspot coordinates for the fuses highlighted in the callout list and their related translated textual description for the fuses in the same way as it does for the other subjects (Engine Management, ABS, and AC) in the Components Location API, allowing for the hover over feature.

This release contains the following new API and enhancement:

• Tyres API (alpha)

Tyres API (alpha)

 Rather than to a fitment guide, this powerful API combines the responses from 5 APIs to provide you with comprehensive data to assist with replacing tyres. The API has a single method call associated with it. For a given MID the response consists of:

Tightening Torque information for Wheel and TPMS Valve nuts

Jacking Mode steps where required

Jacking Points Images

Tyre Pressure Information

Tyre Pressure Monitoring System (TPMS) information (including images and resetting procedures)

This release contains the following new API and enhancements:

• Enhancement to Images API (alpha) via Component Locations API (alpha)
• Enhancement to Repair Times by Genartnr API

Enhancement to Images API (alpha) via Component Locations API (alpha)

The Image API when accessed through the Component Locations (Alpha) API has been enhanced to support the callout lists that helps to identify the critical components present in the System Layout Illustrations for Engine Management, Air Conditioning, Electronic Component Location and Anti-lock braking System.

The Image API response will now include hotspot coordinates for the components highlighted in the callout list and their related translated textual description for the components in the same way as it does for wiring diagrams in the Wiring Diagram API

In addition to this, it will also contain the component images associated to the numbered callouts allowing for hover over hits to be displayed

For Engine management System Layout Illustrations you will also see a non-hotspot section in the API response that lists the component id and related translated component descriptions for the components mentioned in relation to the illustration but not indicated as callouts.

If you wish to suppress the occurrence of these additional image URL in the response a hide parameter can be past in the URL to remove them and reduce the size of the response received.

Enhancement to Repair Times by Genartnr API

We have enhanced the response to indicate whether a part is a primary or secondary part for a particular repair time.

This API still has two call methods.The first call provides the available variants for a given MID and Genartnr. The second call then displays the different operation repair times that include the part linked to the Genartnr  for the given MID and Variant ID.

This release contains the following new API and enhancements:

• Enhancement to Injection and Ignition API 
• Enhancement to Starting and Charging API
• Enhancement to DTC API

Enhancement to both Injection and Ignition API and Starting and Charging API

As part of our focus to improve the quality of the content in our API responses, the response will now include Glow Plug information where available for diesel vehicles. This will include the glow plug “nominal rating”, “activation time” and “part numbers”. The API still has one call method for a given MID.

Enhancement to DTC API

In addition to the DTC API already providing the Probable Cause content for a given DTC, the response now also includes links to the Known Fixes API where we have additional known fixes content available for a given DTC. This can be shown by adding  “known_fixes=true” to the url. Thus providing a more comprehensive response to help troubleshoot the fault codes found by the user. 

This release contains the following new API and enhancements:

• Enhancement to Images API

Enhancement to Images API

In addition to the recent enhancement to the Wiring Diagrams API, we have also extended the Images API to support references to component images (href). This API like before has one call method which provides you with the href for a given MID, Subject and Image ID.

For the case of Component Locations, and MID VOL05471, the subject for example may be air-conditioning, with the image ID as 49094-vol8ac.

This release contained the following new API and enhancements:

• Lifetime Service Summary API
• Operation Lifetime Summary API
• Key Operation Lifetime Summary API
• Enhancement to Wiring Diagrams API

Lifetime Service Summary, Operation Lifetime Summary and Key Operation Lifetime Summary  APIs are here!!!!

As mentioned in our October release, these three new APIs are an evolution of the Common Service Operations API, where we have taken the vast Service Guide information we have to provide intuitive API responses to provide fast and effective service information to the user.

Lifetime Service Summary API

The first in our trio of Lifetime Service APIs provides you with all the service intervals and their corresponding operations for a given Vehicle (MID). This API has two methods associated with it, the first method returns a list of service schedules for the relative variants of a given MID.

The second method call will allow you to find the most suitable service interval and its operations based on the following variables: MID, Service Schedule ID, Service Miles or km, Service Months. The response is then followed by the other intervals available,  as well as the Operation IDs and the intervals they are linked to.

The other optional variables in the second call are the Operation Type ID (Check, Calibrate, replace etc - See documentation for Operation Type IDs), and part information.

Operation Lifetime Summary API

This API in the Service Summary series provides  the user the ability to see the intervals in which a particular operation is required, greatly improving the search capability for those important operations such as timing belt changes. This API has two call methods. The first method call, like with the Lifetime Service Summary API, returns a list of service schedules for the relative variants of a given MID.

The second method call will then provide you with the operational information followed by the Service intervals and respective interval details that the operation is included in. As with the Lifetime Service Summary API, the variables are the same, with the inclusion of Operation ID.

Key Operation Lifetime Summary API

Similar to Operation Lifetime Summary but allowing for service interval information for  multiple Operation IDs to be displayed. There are two method call for this API. The first method call like the previous two APIs, returns the list of service schedules for the relative variants of a given MID.

The second call will provide you with the operational information for the selected operation IDs, followed by the service intervals for those operation IDs. The operation IDs and their associated Service IDs are then displayed at the bottom of the response.  In addition to the MID, Service Schedule ID, Service miles / km, service months and Operation Type ID, this call method allows for up to 20 operation IDs to be entered.

Enhancement to Wiring Diagram API

As part of the continual development to the content rich responses of the Wiring Diagrams API, we have now included image references for the earth point locations along with the annotations for the specific images.

This release contained the following new API and enhancements:

• Enhancement to Service Schedule API
• Transmission API (Alpha)

Enhancement to Service Schedule API

We’ve extended the Service Schedule API response to contain computer readable data ranges values that will enable a developer to select the most relevant service schedule for their customers programmatically. This was done by regexing and extracting content from the service schedule description in the first call method.

Transmission API (Alpha)

This API will provide you with the drain and refill procedure, illustrations (href) as well as the oil grades and capacities for manual, automatic and ASM transmissions. There are two methods associated with this API. The first method returns the list of transmissions available and their transmission IDs for a given MID.

The second method requires a MID and the transmission ID, to return the transmission oil information and drain and refill procedure  for the chosen transmission