RemapdbRemapdb

Remapdb API

Vehicle tuning database API for your application

Build a vehicle selector, tuning calculator, or internal lookup tool with structured JSON data. Read engine details, stock performance, reference stage gains, and available ECU information through the Remapdb API.

Explore API accessSee pricing

Available on API and Max plans. Your developers build the integration. Remapdb returns data; it does not supply, identify, modify, or generate ECU tuning files.

Vehicle and engine records

Search the shared catalog and check the exact engines and fields your application needs.

Vehicle lookup

Build custom make, model, engine, and variant selection flows.

Tuning gains

Read stock and reference stage power and torque where available. Verify suitability for each vehicle.

JSON-ready responses

Work with predictable API responses designed for modern web products.

Custom interfaces

Build your own configurator instead of relying only on the Remapdb Widget.

Platform-ready

Use the API for websites, portals, dashboards, file services, dealer systems, and internal tools.

Build with the API

Your design. Your flow. Our vehicle data.

Use the Remapdb API to build your own vehicle search, performance comparisons, and customer journeys. Your developers control every screen and interaction. This example uses illustrative data.

Build a vehicle finder with the Remapdb API

API possibilities

Use Remapdb data inside your own product experience

Use Remapdb for the vehicle-data part of your product. Your team builds the interface and any quote, order, payment, or file-delivery logic around it.

Custom vehicle configurator

Build your own vehicle search and selection experience using Remapdb vehicle tuning data.

Example: make -> model -> generation -> engine -> tuning result

endpoint
GET https://api.remapdb.com/v2/search?query=audi
GET https://api.remapdb.com/v2/engines/{engine_id}

Tuning gains display

Show stock and tuned performance values inside your own website, dashboard, or portal.

Example: original HP/Nm vs tuned HP/Nm for available stages

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

Vehicle context for your file service

Retrieve vehicle and tuning information for your existing service. File upload, processing, payment, and delivery remain in your own system.

Example: Remapdb returns vehicle data → your own system handles the request

endpoint
// Remapdb: retrieve the selected engine
GET https://api.remapdb.com/v2/engines/{engine_id}
// Your application handles any subsequent file request.

Dealer network tools

Use vehicle and request context inside dealer portals, routing flows, or location-based systems.

Example: selected vehicle + selected dealer + quote request context

endpoint
// Remapdb: search vehicle records
GET https://api.remapdb.com/v2/search?query=bmw
// Dealer routing is implemented in your application.

Product and parts pages

Add vehicle and tuning reference data to product pages. Your team supplies and verifies product-fitment mappings.

Example: vehicle record + your verified product mapping

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

Internal admin tools

Build internal lookup tools for sales, support, quoting, or chip tuning specification database review.

Example: support team searches a vehicle and checks available tuning values

endpoint
GET https://api.remapdb.com/v2/search?query=2.0%20tdi
Explore API docsReview authentication

API workflow

From vehicle lookup to your own interface

The API lets your system request vehicle and tuning data, then render that information inside your own configurator, dashboard, portal, product page, or internal tool.

1

Request vehicle data

Your app requests makes, models, generations, engines, or specific vehicle tuning database records.

2

Receive structured responses

The API returns JSON with the fields available for that record. Handle missing values and unavailable stages in your interface.

3

Render your own UI

You decide how the data appears: configurator, dashboard, product page, portal, or internal tool.

4

Connect the next action

Use selected vehicle context in quote flows, file requests, dealer routing, and internal workflows.

5

Expand when needed

Start with one integration and grow into more endpoints and customer-facing experiences over time.

Read integration best practicesCheck usage limits

Customizations + API

Your catalog, delivered through API v2

Bring your own vehicle data and tuning values into your integration. The Max plan includes both 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 and the v2 endpoints. Responses reflect your saved additions, edited values, and visibility choices. Hiding a parent also removes its vehicles from API results.

Keep your integration in sync

Cache data separately for each account and refresh it after edits. As we update the shared database, review duplicate notices in Customizations and choose which records to keep visible.

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

Video tutorialWatch how to edit your vehicle and tuning dataStarts at 0:56 · 5:09 total
Explore customizationsRead the v2 migration guide

Data coverage

Vehicle and tuning data for custom workflows

Retrieve vehicle identity, engine specifications, and available stage data. An ECU specification describes a unit or related tool; it is not an ECU binary. Check coverage and field availability before building your customer offer.

Vehicle identity

Make, model, generation, year range, variant, and vehicle structure where available.

Engine data

Engine name, fuel type, displacement, stock power, stock torque, and related technical context.

Tuning stages

Stage identifiers and reference performance values where present. These records are information, not flashable calibrations.

Performance gains

Power and torque values from a vehicle tuning gains database, including original and tuned performance values.

Vehicle identity for your own checks

Use returned vehicle details in your own suitability checks. The data does not certify a hardware product or calibration.

Integration metadata

IDs and response fields your system can use to connect Remapdb data to your own interface.

View plan access

Integration patterns

Choose how Remapdb data fits your product

Fetch data through your backend and present it in your own interface. Keep API credentials out of browser code. Your application owns customer actions such as routing an enquiry or placing an order.

Front-end configurator

Use API data to build your own vehicle selector and tuning result UI. Best for custom websites and advanced landing pages.

Back-end service integration

Use your server to request Remapdb data and combine it with your business logic. Best for portals, file-service workflows, and secure workflows.

File-service request flow

Connect vehicle data to file requests, quote flows, and service inquiries. Best for online tuning file providers.

Dealer network routing

Use selected vehicle and dealer context for partner and location-based flows. Best for multi-location tuning companies.

Product-page data layer

Present vehicle information alongside your own independently verified product-fitment mappings.

Internal lookup tools

Build admin, support, sales, and quote-assistance tools for your team.

AI-assisted vehicle lookup

Use the MCP server when supported AI assistants need to search and retrieve vehicle records on API or Max.

Discuss your integration

Developer setup

From API access to first working request

Start with secure credentials, validate requests in staging, then move endpoint by endpoint into your own production flow.

1

Enable API access

Choose API for the shared catalog or Max for API access plus catalog editing. Free, Plus, and Pro do not include the developer API.

3

Review API docs

Check endpoint contracts, parameters, limits, and implementation notes.

6

Test and launch

Validate edge cases, missing values, and usage limits before production rollout.

Explore API accessRead API docs

API capabilities

What the Remapdb API helps your team do

Check the data and access your application needs, then test missing records, errors, and request limits before release.

  • Vehicle hierarchy and search
  • Engine-level reference data
  • Available tuning stages
  • Stock and reference stage performance
  • Available ECU and TCU information
  • Available tools and work methods
  • Structured JSON responses
  • Bearer-key authentication
  • API v2 customized catalog on Max
  • MCP access on API and Max
  • Versioned endpoint documentation
  • Published usage-limit guidance
Visit docs and supportAPI help center

Related features

Choose the right integration path

Widget

Use the Widget when you want the fastest embedded customer-facing experience.

Explore widget

AI integrations

Connect supported AI assistants to Remapdb data through the MCP server on API-enabled plans.

Explore AI integrations

WordPress plugin

Use the plugin if your website runs on WordPress and you want a simpler installation path.

View WordPress plugin

Customizations

Add your own vehicles, edit tuning values, and choose what appears in your catalog. Read your customized data through API v2 on the Max plan.

Explore customizations

Support

See how Remapdb helps with setup, documentation, installation, and technical guidance.

View support

Pricing

Compare plans for API access, websites, branding, quote features, support, and advanced control.

See pricing

FAQ

Questions about the Remapdb API

What does the Remapdb remap database API return?

The API returns vehicle records, engine information, stock power and torque, available tuning stages, and related technical details in JSON. Fields vary by record. Use the documentation to confirm the fields your application needs.

Is this an ECU remapping API or a tuning-file service?

It is an ECU tuning data API. It does not identify, read, edit, generate, or deliver original or modified ECU binary files. If you sell tuning files, your existing software and team remain responsible for file handling, calibration, payments, and delivery.

Can I send an ECU file and receive a tuned file?

No. Remapdb has no file-processing endpoint for that workflow. Widget file attachments are a separate quote-form feature: they send supporting files to the tuning business with an enquiry.

Which plans include API access?

API and Max include REST API and MCP access. Free, Plus, and Pro do not include the developer API. The WordPress plugin connects the hosted widget separately and does not require an API plan.

Can the API return my customized catalog?

Yes. Max includes API access and Customizations. Make edits in the Remapdb app and read your account catalog through API v2. The API plan uses the shared catalog. Catalog editing is not performed through REST requests.

Do I need a developer?

Yes. Your team implements authentication, data retrieval, caching, the interface, and any customer workflow. Remapdb provides documentation and product support, rather than a bespoke website or portal development service.

Does the API include VIN or UK registration lookup?

No. You need a separate provider for automatic VIN or number-plate lookup, then your own matching logic to find the corresponding Remapdb record.

Are tuning gains or hardware compatibility guaranteed?

No. Gains are reference information and fields may be missing for some records. Your team must check the vehicle, hardware, and calibration. Vehicle data alone does not prove that a specific part or tuning box fits.

How do I check coverage and usage limits?

Check the vehicles you serve using the vehicle selector on our home page, then review the API reference and usage-limit documentation before implementation. Contact support for a specific coverage question or expected request volume.

Which API version should I use?

Use API v2 for new integrations and customized catalogs. Existing integrations should follow the migration guide and test their field handling and caching before switching.

Ready to build with Remapdb data?

Add vehicle tuning data to your own product

Use the Remapdb API to power vehicle lookup, tuning gains, configurators, quote flows, dashboards, and custom product experiences.

Explore API accessSee pricing

API and Max plans. Reference data in JSON. Explore related integrations.