For businesses that already supply tuning files

Vehicle data for your tuning file-service platform

Help customers choose a vehicle and review tuning reference information before contacting your file-service business. Embed the Remapdb widget or use the API in your existing platform.

Your business supplies the files. Remapdb provides vehicle and tuning data; it does not sell, modify, generate, or deliver ECU binaries.

How Remapdb fits

Connect a request to the engine the customer selected

A generic file enquiry can arrive without enough vehicle context. Add a vehicle selector backed by the Remapdb catalog, then use the chosen engine record in your own request process. Available ECU and stage information can support that conversation, but it does not identify an uploaded binary or determine the correct calibration for it.

Your setup

Keep data retrieval and file fulfilment separate

  1. Step 1: Select the vehicle

    Use the widget or retrieve records through the API. Confirm the selected engine with the customer where necessary.

  2. Step 2: Send the context to your own workflow

    For a custom integration, your application links the vehicle record to its own request. Remapdb endpoints return data; your own endpoints handle orders and files.

  3. Step 3: Process and deliver through your service

    Your business validates the file, carries out calibration, takes payment, and delivers the result using its existing tools and process.

Before you choose

What your Remapdb subscription provides

Your subscription covers vehicle information and the listed widget or API features. ECU specifications are descriptive data, not downloadable tuning files. Your business handles calibration, file orders, credits, payments, and delivery in its own systems.

FAQ

Questions before you start

Can we upload a .bin file and get a tuned file back?

No. Remapdb does not identify, modify, or generate ECU binaries, through the API or through the team. Use your own calibration tools and service workflow.

What is the difference between file upload and file processing?

Widget file upload attaches a customer’s supporting file to a quote request. Your team receives a download link in the quote email. Remapdb does not examine the calibration or return a modified file.

Can we build a dealer file portal with the API?

The API can provide vehicle and tuning reference data to your portal. Your developers must build accounts, credits, payments, file processing, order status, and delivery separately.

Which page should our developer read first?

Start with the API feature page, then the API reference, authentication, plan-access, and usage-limit documentation. Check the catalog coverage needed for your customer vehicles.

Your next step

Add vehicle context to the service you already run

Review the records your file-service platform needs, then choose an embedded enquiry form or a custom API integration.