Autodata API Developer Blog

RSS Feed

API Release Notes - July 23th 2015

The release contains the following items:

  • DEGAT Procedures API (Beta)
  • Tuning & Emissions (Alpha)
  • Injection and Ignition API (Alpha)

 

DEGAT Procedures API (Beta)

This API provides access to the Autodata DEGAT procedures information. There are two methods associated with this API. The first method is a search, which identifies all the DEGAT procedures that relate to a MID and returns them with descriptions. The second method retrieves the chosen procedure.  

 

Tuning & Emissions (Alpha)

This API provides access to the Autodata Tuning and Emissions information. This API has one method that returns collection of objects containing information about the Tuning and Emissions for a given MID.

 

Injection and Ignition API (Alpha)

This API provides access to the Autodata Ignition and Injection information. There is one method associated with this API, which searches and returns the data for a specific MID.


API Release Notes - July 10th 2015

This release contains the following new API:

  • Tightening Torques API
  • Retrieve repair time for a specific operation an ad_part_id API
  • Enhancements to TPMS API

 

Tightening Torques API

This API allows the technical data we collate relating to tightening torques to be returned for a given Model Identification Number (MID). This API has one method and returns the tightening torque instructions which include values, procedures and images in three groups;

  1. Cylinder head
  2. Other engine tightening torques
  3. Chassis tightening torques

 

Reverse Repair Times API by ad_part_id

This is an enhancement to our original ‘Reverse Repair Times API (Alpha)’. We have extended it to be able to support both the functionality of looking up the repair times by a part based on the Techdoc Part numbers known as Genartnr. Which was previously released as our ‘Repair times by Genartnr’ API. As well as by our Autodata part numbering known as ad_part_id. 

It was the later that was released this time and can now be found in our interactive documentation below the ‘Repair times by Genartnr’.

This API has two method calls, the first is a search method, and requires a Model Identification Number (MID) and a ad_part_id number. This brings back all the possible variations of a part that effects the time it takes to do the relevant repair. With related “href”, links to allow the second call to be made. The second method drills down using the ‘variant_id’ returned in the first response. It returns the part description, the repair times, component description it relates to and the related genartnrs to do the repair.

 

Enhancements to TPMS API

We have enhanced the TPMS response by adding tightening torque wheel information from our database to the API response.

 

 

API Release Notes - June 25th 2015

This release contains the following new API:

  • Service Indicator API
  • Enhancement to the Tools Referance API
  • Retrieve repair time for a specific operation and part ID
  • Know Problems and Fixes API (Beta)
  • Reverse Repair Times API (Alpha)


Service Indicators API

The Service Indicators API provides the necessary steps to be taken to turn off the service warning indicators for a particular vehicle. Although vehicles from the same manufacture sometimes share the same steps, this is not always the case. There are also a number of different types of warnings covered ranging from the ‘Engine Oil Change Indicator’ to the ‘Fixed/Longlife Service Intervals’ warning.

For one Autodata Vehicle Identification number (MID) there are often more than one set of procedures for service indicators. We therefore have structured this API in a similar way to others, where we have two calls. The first called ‘Search service indicators ids’ returns a list of options, each including an ID and a description and a URL to make the second call. 

The second API method is called the ‘Retrieve service indicators’ method and uses the “service_indicator_id” in its URL along with the MID to return the steps required to be followed, allowing the particular service indicator to be re-set. 

 

Enhancement to the Tools Reference API

We have added in a new section called "tool_full_text" this is a text string and contains the full textural description we have for the related tool. Some of this content may appear to be repeated in the other sections of the response where we want to present the data in as granular way as possible.

By making this addition we feel that this API no-longer needs to be an Alpha API, we do not intend at this point, to be making any changes to this API before we produce a version 2. 

 

Retrieve repair time for a specific operation and part ID

It allows the time that it takes to undertake a specific operation for a part to be returned. This is a third level call for the existing API methods and will provide a filtered view on the response of the other methods. As well as the time required to complete the operation, the response also lists the compoents required to either remove and install, or check and adjust as well.

 

Know Problems and Fixes API (Beta)

This API has been divided into two main parts the first provides access to the Autodata Known Problem Areas information, the second part providing the Fixes and Bulletins information for the Problem Areas. Both parts are made up of two calls, the first to search for the options available, and the second, to drill further into the chosen option. We have embeded the required URL to drill down to the problem areas of concern and also to the related fixes that need to be performed. 

 

Reverse Repair Times API (Alpha)

This API is still being developers but we are releasing it to get feedback from our developer community. This API has two method calls the first is a search method and requires a Model Identification Number (MID) and a Genartnr number. This brings back all the possible variations that effects the time it takes to do the relevant repair, each of these have a ‘variant_id’ and a URL for the second call which drill downs and access the information related to a chosen variant. 

 

 

API Release Notes - June 11th 2015

This release contains the following new API:

  • Auxiliary Drive Belt API (Beta)
  • Air Conditioning Recharge API
  • Lubricants and Fluids API (Beta)

 

Auxiliary Drive Belt API (Beta)

This API provides access to the Autodata Auxiliary Drive Belt Procedures information. There are two methods associated with this API, the first method returns a collection of Auxiliary Drive Belt Procedure ids for a given Autodata model identification number (MID) and is called the 'Search Auxiliary Drive Belt Procedure ids'. You may for example have a choice of two "auxiliary_drive_belt_id" returned, covering either the front or rear Auxiliary Drive Belt. 

The second method is called 'Retrieve Auxiliary Drive Belt Procedures' and returns the Auxiliary Drive Belt Procedure object, containing all the possible procedures, images and steps that are likely to need to be performed, for the specific Auxiliary Drive Belt selected from the first method call response. 

 

Air Conditioning Recharge API

This API provides access to the Autodata Air Conditioning filling capacity information and images, which historically has been compiled as a section of the technical data subject. It has one methods, which returns all the data related to a valid MID. This API also contains links to the 'Notes API'.

 

Lubricants and Fluids API (Beta)

This API builds on the work that we have undertaken as part of the Engine Oil API. It provides access to the Autodata Lubricant and Fluid information (including engine oil), which historically has been compiled as a section of the technical data subject. This API can return information about the types of lubricants and fluids used by the following systems:

  • ASM Transmission
  • Automatic Transmission
  • Brakes
  • Clutch
  • Coolant
  • Diesel Particulate Filter (DPF)
  • Differential
  • Manual Transmission
  • Power Steering
  • Selective Catalytic Reduction (SCR)
  • Two Stroke

This API has three methods, the first method returns a collection of lubricant and fluid information available for a given MID and is called the 'Search for lubricants and fluids'. This response always has all the sections as listed above, however where there is no information recorded for a section, for a given MID we set “active” to false and “href” to null in the response. Where there is data we set the "active" key to true and populate the "href" with a URL which can be used to make the second method call, to pull back the lubricant and fluid information for the selected system. 

The second method is called "Retrieve lubricants data for selected system"; as mentioned above, will return in this response, detailed information about the lubricant and fluids for the specific system selected. The response includes information regarding grades, classifications, types and capacities.

The third method will retrieve all the lubricant and fluid information for a give MID in one go, this is a longer response but will be useful for applications where there is a need to access all the content rather than a subset.

Note: Please be aware that this API also contains links to the 'Notes API', these are accessed by URL included in the response, and will often contain a lot of useful information.

 

 

 

API Release Notes - 28th May 2015

Camshaft Drive Replacement API

We have released our Camshaft Drive Replacement API. This API retrieves the detailed procedures that need to be performed when replacing the timing belt and timing chains for the chosen vehicle. This API includes illustrations to support the work that is required to be undertaken.   

API release Notes - 30th April 2015

The release contains the following items

  • Key Programming API (Alpha)
  • Battery disconnection and reconnection API (Beta)
  • Minor enhancement to Engine Oil API
  • Minor enhancement to Service Schedules API
  • Updates to Development Portal I/O Docs Page

 

Key Programming API (Alpha)

This API provides access to the Autodata Key Programming Procedures information, it is still an Alpha so we are releasing it to the I/O docs page for customer feedback only at this stage. 

There are two methods associated with this API, the first method returns a collection of Key Programming Procedure ids for a given MID and is called the 'Search Key Programming Procedure ids'. The second is called 'Retrieve Key Programming Procedure' and returns the Key Programming Procedure object, containing all the possible procedures and steps that are likely to need to be performed.


Battery disconnection and reconnection API (Beta)

This API provides access to the Autodata Battery Replacements information. 

There are two methods associated with the API, the first method 'Search Battery Replacement ids' returns a collection of Battery Replacement ids and descriptions for a given MID. The second method 'Retrieve Battery Replacement' returns the Battery Replacement object containing all the procedural steps, warnings, notes, images etc. 

 

Minor enhancement to Engine Oil API

We added a "range" key associated with the boolean values true or false to indicate if there are a range of temperatures, improving the consistency of the API response. 

.

Minor enhancement to Service Schedules API

We used to just show the services intervals advisory warnings as unformatted text strings associated with the "service_advisory_message" attribute. Now we are offer a more formatted response called "formatted_service_advisory_message" that will hopefully help developer understand how to more optimally display this information to their end users.

 

Updates to Development Portal I/O Docs Page

We have made some updated to the I/O Docs page on the Developer Portal and added in a 'NEW!' label to indicate API that have been released in the last two weeks.


API Release Notes - 16th April 2015

Enhancement to Tyre Pressure Monitoring System (TPMS) API

We have added a new key in the API response in the Special Tools section called 'tool_full_text", this will return all the information about the Specials Tools in a text string.

 

Enhancement to Diagnostic Trouble Code (DTC) API

Following on from enhancements we have made in subsequent releases, we have extended this API to return information related to On-board Diagnostic Codes (EOBD, OBD2).

 

ACES Vehicle Look up Method

We have added the ability to do ACES Look ups through our Vehicle Look up API. This API takes four parameters VehicleID, BaseVehicleID, Engine ConfigID, BaseEngineID. A look up can be made on any combination of these parameters, however the more you have the closer we can response with a one to one match.

 

Replacement Times API Enhancements

Enhanced the response of the Replacement Times API to display information related to repeat times. This brings the API response in line with the Services Schedules API which already returns this additional level of detail to guide when work needs to be carried out.

 

Fixes

Addressed an issue that was preventing the API from supporting the nl-be and pt-br cultures.

API Release Notes - 1st April 2015

Tyre Pressure Monitoring System (TPMS) API (BETA)

We have released as a (BETA) our TPMS API. This API is marked (BETA) because we believe that there is still going to be slight changes to the API response but no significant changes which would cause us not to recommend starting to evaluate build against it.

This API has two methods:

  1. Search TPMS ID - This GET method requires a Autodata Model Identification Number (MID) and returns in the response all the TPMS ID that relate to it. There is also a 'href' to take you to the next method call (see below) and retrieve the information for the TPMS ID.
  2. Retrieve information for a TPMS ID - This GET method required a Autodata MID, and the TPMS ID and it returns detailed information, procedures and images. This is a large API response please see the relevant technical documentation page for more details.

 

Tools Referance API (ALPHA)

We have release as an (ALPHA) our Tools reference API. This API is marked (ALPHA) because we are expecting that this API may change, we would be interested in getting this API reviewed by developers using our API and will indeed consider amending the API based on feedback received. Please provide any feedback through the contact form on the blog or via the customer-integration@autodata-group.com email address.

This API has one method which as the name suggests provides access to the Autodata Tools information. Please see the relevant  technical documentation page for more details.


API Release Notes - 26 March 2015

Version 1 Vehicle by MID Look-up

This release we have made an enhancement to the Version 1 Vehicle by MID Look-up. We have extended the response so that it now contains the attribute "Veh_type" in the response. This will allow developers to identify what type of vehicle it is, for example if it is a Hybrid Petrol Cars or a Bi-fuel Cars. Please take a look at the technical documentation to see more information.

 

Error Codes

We have enhanced the error codes information that will be returned and documented this in the Additional Information section of this Developer Portal.

API Release Notes - 19 March 2015

API Release Notes – 19th March 2015

Enhancement to Diagnostic Trouble Codes API

We have added in an attribute called ‘system’ So that we can show which system the fault relates to. The system can also now be used as a parameter of the URI and passed into the URI as a query, to filter the API response to a specific system.

System values that can be used as a query parameter and returned in the response are listed below:

  • Abs  - standing for Anti-lock braking system
  • Eman  - standing for Engine Management system
  • Tran  - standing for transmission system
  • Immob  - standing for Immobilizer system
  • Srs  - standing for Supplemental Restraint System (Air bags)
  • Ac  - standing for Air conditioning system

 

Enhancements to our support for KBA

We have improved our support for the KBA ID in our vehicle look up by KBA API method. Prior to this enhancement the KBA ID needed to be passed as a parameter in the URI in a structured format of four characters with an underscore then three characters. The four characters are the KBA Manufacturer no. and the three characters are the KBA key no. Feedback from our development community has caused us to remove the need for this structure, our API will now support the following formats.

  • 0005 622
  • 0005622
  • 0005_622

 

Enhancement to Engine Oil API

The response has been extended to include some additional attributes which we hope will allow consumers of the API to obtain more useful and granular information. The previous functionality we have related to the ‘capacity’ key and the ‘other key’ remain the same.

We have added the following new keys:

  • range - this is a boolean. If it is true it means that there are a range of engine oil capacity values. If it is false then there is only one capacity value
  • minimum - If the range is true this key will show the lower value in the range. if range is false this key will be null
  • maximum - If the range is true this key will show the largest value in the range. if range is false this key will be null
  • value - If range is true this key will be null, if range is false this key will show the same value as capacity key
     


Enhancement to Services Schedule API

Repeat services interval information has been added to the API response. Previously we were showing this information but only as part of the text string associated with the Keys interval_description_for_miles and interval_description_for_kms 

  • repeat_months
  • repeat_hours
  • repeat_miles
  • repeat_kms

[ Previous | Page 4 of 5 | Next ]