Vehicle catalog API

Your vehicle experience. Our tuning database.

Build vehicle search, selectors and tuning results into your own website or software with the Remapdb vehicle tuning database API.

A free trial catalog on every plan. Full catalog access on API and Max.

Integration
REST API v2
Response format
Structured JSON
Free trial
No expiry

Explore it yourself

Vehicle catalog API playground

Try an example or enter your own details. See the API’s results, explore the full JSON, and use the request in your integration.

Try the vehicle catalog

Live API

Search vehicles or read an engine’s specifications and tuning gains.

Try an example

Enter an engine ID for details, or a make, model or engine for search.

Build with the API

Your design. Your flow. Our vehicle data.

See how a custom vehicle finder can turn API data into selections, tuning results and performance comparisons. This illustrative application shows one possible design.

Build a vehicle finder with the Remapdb API

API possibilities

Build your own vehicle experience

Use the remap database API wherever a vehicle choice needs clear specifications and tuning information. Your application controls the design and what happens next.

Custom tuning websites

Build a vehicle selector and tuning comparison that match your website, with your own layout, navigation and calls to action.

Quotation workflows

Attach the chosen engine and available tuning figures to your own enquiry or quotation flow, so your team starts with vehicle context.

Dealer portals

Give dealers a consistent vehicle lookup inside your portal. Your system handles dealer selection, routing and customer follow-up.

File-service requests

Add catalog vehicle details to your existing file-request form. File processing, calibration, payments and delivery remain in your own service.

Product and parts pages

Present vehicle specifications beside your products and your own verified fitment mappings. Use the catalog as vehicle context for your product information.

Sales and support tools

Help staff find an engine, compare available stages and check equipment information without leaving your internal application.

Endpoint guide

The requests behind your integration

See what each endpoint does and where it fits in your product. Authenticate on your server with Authorization: Bearer <API_KEY>. Replace placeholder IDs with the values returned by your requests.

Find a vehicle directly

Search manufacturers, models, generations and engines from one text field. Use the returned engine ID to open its details.

Example: A visitor searches Audi, then selects the matching engine.

Endpoint
GET https://api.remapdb.com/v2/search?query=audi

Start a vehicle selector

List the vehicle types available to the account as the first step in a guided vehicle selection.

Example: Your selector begins with the vehicle categories the account can access.

Endpoint
GET https://api.remapdb.com/v2/types

Choose a manufacturer

Load manufacturers for the selected vehicle type. Use cursor pagination when the list continues beyond the first page.

Example: Choosing a vehicle type loads its available manufacturers.

Endpoint
GET https://api.remapdb.com/v2/manufacturers/type/{type_id}

Show the available models

Retrieve the selected manufacturer’s models and use their IDs to continue through the catalog.

Example: A manufacturer choice updates the model dropdown in your interface.

Endpoint
GET https://api.remapdb.com/v2/models/manufacturer/{manufacturer_id}

Narrow down the generation

List a model’s generations so visitors can choose the relevant version before selecting an engine.

Example: A model selection reveals its generations and available year information.

Endpoint
GET https://api.remapdb.com/v2/generations/model/{model_id}

Select an engine variant

List the engines within a generation. Keep the selected engine ID for the detailed specifications and tuning request.

Example: Your final selector shows the engines available for that generation.

Endpoint
GET https://api.remapdb.com/v2/engines/generation/{generation_id}

Present specifications and gains

Read original performance, available tuning stages and associated engine information. Use these fields in your own comparison or quotation interface.

Example: Display original power and torque beside the returned Stage 1 and Stage 2 figures.

Endpoint
GET https://api.remapdb.com/v2/engines/{engine_id}

Data coverage

What the vehicle tuning database returns

Combine the available fields into a useful vehicle view. Coverage varies by record and by the catalog your account can access.

Vehicle hierarchy

Vehicle types, manufacturers, models, generations and engine variants, with IDs that link the selection steps together.

Engine specifications

Engine names and codes, capacity, cylinders, fuel and engine type where the selected record contains them.

Original performance

Original power and torque, plus available performance and dyno data for your result cards or charts.

Tuning stages

Available stage values, stage IDs and any recorded modification requirements. Compare each stage with the original engine figures.

ECU and TCU information

The ECU and TCU records associated with an engine, including the manufacturer and model details available in the catalog.

Tools, methods and options

Reading tools, work methods and tuning options linked to the engine, ready to include in your technical view.

Developer setup

From API access to your first integration

Set up access, try your first request, and bring the results into your own application.

1

Activate your catalog access

Open API → Vehicle catalog in your account and activate free trial access. The page lists the manufacturers included in your trial.

3

Review the response contract

Check the endpoint parameters, available fields and pagination in the API reference. Keep missing values and account-specific data in mind.

6

Test and expand

Test missing fields, pagination and request limits. Scope cached data to the account, and move to API or Max for the full catalog.

Customizations + API

Your catalog, delivered through API v2

Bring your own vehicle data and tuning values into your integration. Max includes API access and Customizations, so your app can use the catalog you manage in Remapdb.

Make it yours in the app

Add vehicles, adjust tuning stages and manage equipment in Customizations. Your changes apply only to your account, leaving the shared Remapdb database unchanged.

Read your changes through v2

Use your existing API key. Responses reflect saved additions, edited values and visibility choices. Hidden or unavailable parents also exclude their descendants from results.

Keep your integration in sync

Cache responses by account, language and catalog profile, and refresh after edits. Review duplicate notices as the shared database grows and choose what stays visible.

The API plan returns the shared catalog. Pro includes Customizations for your widget; choose Max to use your customized catalog through the API. Catalog editing happens in the app, not through REST requests.

API essentials

Know what to expect

FAQ

Questions about Vehicle catalog API

Can I try the vehicle catalog API for free?

Yes. Every account can activate a trial catalog, including Free accounts. It has no expiry and includes the vehicles within the manufacturers listed on your account’s Vehicle catalog page. Full catalog access requires API or Max.

Does the API include tuning files?

The API provides vehicle and tuning reference data, including the available stages, performance figures and equipment information for an engine. It does not supply ECU tuning files.

Can I use my own interface instead of the widget?

Yes. The remap database API returns JSON for your own website or application. Search or follow the vehicle hierarchy, then display the engine data in your own design. Use the hosted widget when you want the vehicle selector, results and quote form ready to embed.

Does the vehicle catalog API also search UK number plates?

UK registration lookup uses the separate POST /v2/vrm/uk/lookup endpoint and its shared lookup balance. The catalog endpoints search vehicle records and retrieve engine details without using your UK lookup balance.

Will my key change when I upgrade?

No. Your existing credentials stay the same when you move from the trial catalog to full access. If paid API access later ends, those credentials return to the trial catalog.

Can I use catalog customizations through the API?

Yes, with Max. API v2 exposes the account-visible catalog, including your private records and customizations. Use stable record and stage IDs to keep shared and private data correctly linked.

Your application. Remapdb data.

Build your next integration

Start with an account, choose the access your project needs, and connect your own workflow.