DEV Community

Abe Darwish for CarsXE

Posted on

2 2

Use Cases: Tire Sizes API

The general rule of thumb is that tires can last anywhere between 25,000 to 50,000 miles before they need to be replaced.1 That means that going into year 2 most car owners start thinking about getting new tires.

Tire companies that have worked with CarsXE API have increased their conversions by over 30% because they provided a quick and easy solution for their customers with the least amount of friction.

As customers look online and locally for good deals tire shops need to quickly figure out what vehicle the user is driving so they can find all the options that fit that car. The provider that offers the least friction to the customer is likely to capture that buyer.

Here's the problem:

Most customers don't know what's the make, model, year & trim of the vehicle they drive.

Answer:

Most customers do know their license plate number or can figure out where to find the VIN (Vehicle Identification Number).

CarsXE API provides all sorts of vehicle data through its API. One of the largest use cases of the Vehicle Specifications API is tire companies that would like to access the specific tire size of a vehicle from a VIN.

Companies also use our Vehicle Plate Decoder to get the VIN from a license plate which could then be used to get the tire size.

Let's see it in action.

Step 1

Ask the customer for a license plate number & state. (You could also use the Vehicle Plate Image Recognition to extract the license plate number from an image.)

Step 2

Get vehicle data from the license plate. More on that here:

Step 3

Get tire size from VIN extracted. More on that here:

Step 4

Congrats! From a license plate, we were able to find the tire size of the vehicle attached to the plate.

This process gives the user less friction and allows them to know their tire size. As you can see we could also expand this power beyond tire sizes as the Vehicle Specifications API provides many useful nuggets of information on the vehicle.

API Trace View

How I Cut 22.3 Seconds Off an API Call with Sentry πŸ‘€

Struggling with slow API calls? Dan Mindru walks through how he used Sentry's new Trace View feature to shave off 22.3 seconds from an API call.

Get a practical walkthrough of how to identify bottlenecks, split tasks into multiple parallel tasks, identify slow AI model calls, and more.

Read more β†’

Top comments (1)

Some comments may only be visible to logged-in visitors. Sign in to view all comments.

nextjs tutorial video

Youtube Tutorial Series πŸ“Ί

So you built a Next.js app, but you need a clear view of the entire operation flow to be able to identify performance bottlenecks before you launch. But how do you get started? Get the essentials on tracing for Next.js from @nikolovlazar in this video series πŸ‘€

Watch the Youtube series

πŸ‘‹ Kindness is contagious

Please leave a ❀️ or a friendly comment on this post if you found it helpful!

Okay