Nitto Tire API

Overview

There are two versions of the Nitto Tire Finder API: the Legacy version (v3) and the Current version (v4). The Legacy version is deprecated and will be phased out in the future. To support Nitto transitioning from the older v3 to the new v4, a compatibility layer has been implemented within the v4 version.

The legacy API (version 3.6.1) is running at https://api.nittotire.com with instructions available here.

The new API (version 4.2.5) is running at https://api.nittotire.entrinix.com with instructions available here.

Changes

Version 4 of the Nitto Tire Finder offers the following improvements/changes:

• XML has been deprecated for standard JSON format. JSON has become the dominant choice over XML in REST APIs due to smaller payloads, faster parsing and processing, better support in modern programming languages, and easier to work with than XML.
• Support for multiple brands (Default is Nitto Tire).
• Support for failed fitments
  • When a vehicle is selected for fitments, the failed fitments can be accessed. This tells us why a particular tire was not recommended.
  • This can be turned off for performance reasons.
• Product statistics summaries are available to provide an overview of the Nitto tire lineup, highlighting counts for each metric of tire.
• Support for filters for vehicle types.
  • Each vehicle type can have its own maximum plus size, as well as specific tolerances for overall outside diameter (OAD) and overall section width (OAW).
  • A vehicle type can be assigned an offset speed rating, which adjusts the recommended tire speed rating relative to the original equipment (OE) tire. For example, a -1 offset for passenger cars means that if the OE tire is V rated, the system will recommend a tire with one lower speed rating (H), accompanied by a warning. A -2 offset would recommend a U-rated tire. Conversely, a +1 offset means only higher speed ratings—Z, W, Y, or (Y)—will be recommended. All other criteria, such as load capacity and compatibility with the OE vehicle, must still be met for a tire to be recommended.
• Fully cached results improving response times from 500ms to 40-50ms.

Compatibility Layer

To ease the transition to the new API, a compatibility later has been added to the new API which follows the exact output as the old API.

Version 3 API Endpoints

• https://fitments.nittotire.com/service
• https://fitments.nittotire.com/service/json
• https://fitments.nittotire.com/service/size
• https://fitments.nittotire.com/service/size/json

Version 4 API Endpoints

The following endpoints are available on the new system which mirror the results.

• https://api.nittotire.entrinix.com/service
• https://api.nittotire.entrinix.com/service/json
• https://api.nittotire.entrinix.com/service/size
• https://api.nittotire.entrinix.com/service/size/json

Last Updated: Apr 22, 2025