Find the right vehicle
Search across the catalog or guide customers through vehicle type, manufacturer, model, generation and engine.
Vehicle catalog API
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.
Search across the catalog or guide customers through vehicle type, manufacturer, model, generation and engine.
Read original power and torque, available tuning stages, dyno curves, ECU information and recorded reading tools for an engine.
Use the JSON response in your own configurator, quotation flow or internal tool. You control the interface and the next step.
Explore it yourself
Try an example or enter your own details. See the API’s results, explore the full JSON, and use the request in your integration.
Build with the API
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 your own vehicle lookup with the remap database API. The example compares reference values; it is not a supplied application, a parts-fitment guarantee or a tuning-file service.
Vector is an illustrative application built for this video. Brand, model, generation and engine dropdowns lead to a custom performance brief with its own typography, layout and interactive chart. It demonstrates how developers can build their own customer experience with Remapdb API data. This design is not a supplied widget or an included application template.
The fictional selection is Example Motors, GT, 2022–2026, 2.0 Turbo. An isolated sample engine response supplies the displayed figures: 150 hp and 270 Nm original, and 180 hp and 320 Nm estimated Stage 1. Power and Torque controls switch the comparison chart and calculate the difference: 30 hp (20%) or 50 Nm (approximately 19%). Displacement, cylinders and fuel also come from the response. The chart compares these values; it does not represent a measured dyno run. The vehicle and figures are illustrative.
A production application keeps its API key on its server and uses authenticated Remapdb API requests. Your developers implement the interface and interactions. Direct API access requires API or Max. This recording uses no live credentials, makes no live API call, and submits no enquiry.
Voiceover: Build your own vehicle finder with our API. Design the selection, results, and comparisons. Remapdb supplies the data. Your developers build the experience.
API possibilities
Use the remap database API wherever a vehicle choice needs clear specifications and tuning information. Your application controls the design and what happens next.
Build a vehicle selector and tuning comparison that match your website, with your own layout, navigation and calls to action.
Attach the chosen engine and available tuning figures to your own enquiry or quotation flow, so your team starts with vehicle context.
Give dealers a consistent vehicle lookup inside your portal. Your system handles dealer selection, routing and customer follow-up.
Add catalog vehicle details to your existing file-request form. File processing, calibration, payments and delivery remain in your own service.
Present vehicle specifications beside your products and your own verified fitment mappings. Use the catalog as vehicle context for your product information.
Help staff find an engine, compare available stages and check equipment information without leaving your internal application.
Endpoint guide
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.
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.
GET https://api.remapdb.com/v2/search?query=audiList 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.
GET https://api.remapdb.com/v2/typesLoad 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.
GET https://api.remapdb.com/v2/manufacturers/type/{type_id}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.
GET https://api.remapdb.com/v2/models/manufacturer/{manufacturer_id}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.
GET https://api.remapdb.com/v2/generations/model/{model_id}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.
GET https://api.remapdb.com/v2/engines/generation/{generation_id}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.
GET https://api.remapdb.com/v2/engines/{engine_id}Data coverage
Combine the available fields into a useful vehicle view. Coverage varies by record and by the catalog your account can access.
Vehicle types, manufacturers, models, generations and engine variants, with IDs that link the selection steps together.
Engine names and codes, capacity, cylinders, fuel and engine type where the selected record contains them.
Original power and torque, plus available performance and dyno data for your result cards or charts.
Available stage values, stage IDs and any recorded modification requirements. Compare each stage with the original engine figures.
The ECU and TCU records associated with an engine, including the manufacturer and model details available in the catalog.
Reading tools, work methods and tuning options linked to the engine, ready to include in your technical view.
Developer setup
Set up access, try your first request, and bring the results into your own application.
Open API → Vehicle catalog in your account and activate free trial access. The page lists the manufacturers included in your trial.
Open API Keys & Usage and use a key with vdb_read permission. Keep it on your server and send it as a Bearer token with API v2 requests.
Check the endpoint parameters, available fields and pagination in the API reference. Keep missing values and account-specific data in mind.
Search directly or follow vehicle type, manufacturer, model, generation and engine. Request the selected engine’s details and available tuning stages.
Present the JSON in your own selector, results page or internal tool. Connect the chosen vehicle to your existing business workflow.
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
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.
Add vehicles, adjust tuning stages and manage equipment in Customizations. Your changes apply only to your account, leaving the shared Remapdb database unchanged.
Use your existing API key. Responses reflect saved additions, edited values and visibility choices. Hidden or unavailable parents also exclude their descendants from results.
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
Let customers search directly or guide them through vehicle choices. Both routes lead to an engine record, ready for your own website or software.
Bring available engine specifications, original performance and tuning results into one view. Show the details your customers need for comparisons, quotations or internal workflows.
Every plan includes a trial catalog with no expiry. Start with the manufacturers listed in your account, then upgrade when you need the full database.
Keep building
Request parameters, response fields and examples for the catalog endpoints.
Read the guideopen_in_newActivate the trial and understand full catalog access.
Read the guideopen_in_newCreate keys and authenticate your server-side integration.
Read the guideopen_in_newUpdate an existing integration and understand the current response format.
Read the guideopen_in_newFAQ
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.
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.
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.
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.
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.
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.
Connected tools
Explore the UK vehicle lookup API from Remapdb. Find vehicle details and estimated tuning gains by number plate, with free test registrations and a shared lookup balance.
Explore the APIExplore the Remapdb ECU observation API: ECU identification, binary inspection, map candidates, raw grids and file comparison. Analyze a file in the playground.
Explore the APILook up diagnostic trouble code definitions with the Remapdb DTC API. Filter by manufacturer, search descriptions, check batches and try live code lookup.
Explore the APIConnect your AI assistant to Remapdb’s vehicle data and API tools through MCP.
Your application. Remapdb data.
Start with an account, choose the access your project needs, and connect your own workflow.
Questions about your use case? Talk to our team.