Vehicle selection for your portal
Use make, model, generation, and engine records in your existing interface. Your developer connects the selected record to your own order or enquiry.
For businesses that already supply tuning files
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
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.
Use make, model, generation, and engine records in your existing interface. Your developer connects the selected record to your own order or enquiry.
Display the available engine, performance, stage, and ECU information. Review missing fields and verify relevance before accepting work.
The widget on Pro and Max can collect ECU reads and other supporting files with an enquiry. Your team receives a download link; no automatic tuning or file-processing step follows.
Your setup
Use the widget or retrieve records through the API. Confirm the selected engine with the customer where necessary.
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.
Your business validates the file, carries out calibration, takes payment, and delivers the result using its existing tools and process.
Before you choose
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
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.
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.
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.
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.
Explore the features
See how each feature works, what it includes, and which plan gives you access.
Review available records, authentication, and response examples for a selector in your existing portal.
Explore APISee how a customer can add supporting files to an enquiry on Pro or Max, ready for your team to review.
Explore widgetCompare shared-catalog access with the combination of editing, widget features, and API access on Max.
Compare plansYour next step
Review the records your file-service platform needs, then choose an embedded enquiry form or a custom API integration.
Your business supplies the files. Remapdb provides vehicle and tuning data; it does not sell, modify, generate, or deliver ECU binaries.