Identify the ECU
Read the available manufacturer, family, variant, and hardware or software identifiers, with a clear confidence level.
ECU observation API
The Remapdb ECU observation API analyzes raw ECU binaries and returns structured reports. Identify the ECU, inspect file condition, explore candidate maps and raw grids, or compare two files through background jobs.
Included with active API and Max plans.
Read the available manufacturer, family, variant, and hardware or software identifiers, with a clear confidence level.
Inspect file condition, find candidate maps, and retrieve raw grid values for closer review in your own interface.
See exact byte differences alongside candidate-map comparisons, including changed cells and realigned matches.
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.
API possibilities
Build ECU identification, inspection and comparison into your own product. Your application controls the upload flow, review process and presentation of each report.
Identify an uploaded ECU file and attach available hardware or software numbers to the request before your team reviews it.
Bring file-condition findings, supported checksum checks and identification confidence together in your team's review screen.
Show how two supplied files differ, with exact byte counts and candidate-map changes in one comparison view.
List candidate tables, then request raw values for a selected map to display as a grid, heatmap or surface in your interface.
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.
Read the supported operations and current file-size, entry and grid limits, plus retention periods. Use this endpoint to check service access before submitting files.
Example: Check service availability before enabling uploads in your application.
GET https://api.remapdb.com/v2/ecu/capabilitiesSend one raw binary in the multipart file field. The response returns an account-owned file ID, checksum, size and expiry for later operations.
Example: Upload ecu.bin and save its returned file_id for an inspection.
POST https://api.remapdb.com/v2/ecu/files
Content-Type: multipart/form-data; boundary=remapdb-example
--remapdb-example
Content-Disposition: form-data; name="file"; filename="ecu.bin"
Content-Type: application/octet-stream
<raw binary bytes>
--remapdb-example--Queue an identity-only report with available ECU and hardware or software identifiers. This endpoint accepts file_id alone and returns a job to follow.
Example: Find the ECU family and supported identifiers without requesting a full inspection.
POST https://api.remapdb.com/v2/ecu/identifications
Content-Type: application/json
Idempotency-Key: <unique-request-identifier>
{
"file_id": "{file_id}"
}Queue identification, file-condition checks and candidate-map observations together. Set limit for the initial descriptor page; the stored download includes all candidates.
Example: Inspect one upload, show 20 candidates initially, and download the full map list.
POST https://api.remapdb.com/v2/ecu/analyses
Content-Type: application/json
Idempotency-Key: <unique-request-identifier>
{
"file_id": "{file_id}",
"operation": "inspect",
"limit": 20
}Queue a comparison of reference and comparison files. Results separate exact byte changes from candidate-map matches and changes in their cell values.
Example: Compare two versions of a supplied binary without assuming either is original or tuned.
POST https://api.remapdb.com/v2/ecu/comparisons
Content-Type: application/json
Idempotency-Key: <unique-request-identifier>
{
"reference_file_id": "{reference_file_id}",
"comparison_file_id": "{comparison_file_id}",
"limit": 20
}Queue a scan for candidate tables. Download all saved map IDs, positions and dimensions once, or read individual pages from the completed job's details.
Example: Browse every map candidate locally before opening one as a raw grid.
POST https://api.remapdb.com/v2/ecu/map-scans
Content-Type: application/json
Idempotency-Key: <unique-request-identifier>
{
"file_id": "{file_id}",
"limit": 20
}Authorize a short-lived storage download of the complete candidate descriptor list. Fetch the returned Location without your API key, then browse the JSON locally.
Example: Download all 701 candidates in one file without repeatedly loading the full result through the API.
GET https://api.remapdb.com/v2/ecu/jobs/{job_id}/artifacts/mapsQueue raw-grid extraction using the original file and a map ID from its completed scan or inspection. Read grid.values and available axes from the new job's details.
Example: Turn a selected map candidate into rows of numbers for your table or heatmap.
POST https://api.remapdb.com/v2/ecu/map-grids
Content-Type: application/json
Idempotency-Key: <unique-request-identifier>
{
"file_id": "{file_id}",
"scan_job_id": "{scan_job_id}",
"map_id": "{map_id}"
}Read the saved job status without restarting analysis. Inspect status and error together: a failed job can still be retrieved successfully with HTTP 200.
Example: Poll every two seconds or slower while showing progress in your own interface.
GET https://api.remapdb.com/v2/ecu/jobs/{job_id}Fetch the compact report after completion. It contains the operation's findings, counts and notices without the larger map entries or cell arrays.
Example: Show the identification outcome or changed-byte count in a request overview.
GET https://api.remapdb.com/v2/ecu/jobs/{job_id}/resultRetrieve expanded observations for the completed operation, including map descriptors, candidate comparisons or raw grid values and axes.
Example: Load the grid cell array only when a user opens that map.
GET https://api.remapdb.com/v2/ecu/jobs/{job_id}/detailsPrevent further use of an uploaded file and schedule its removal. Retained reports follow their own expiry, while physical cleanup can wait for active processing to finish.
Example: Remove the uploaded binary when your review workflow is finished.
DELETE https://api.remapdb.com/v2/ecu/files/{file_id}Data coverage
Choose the observations your interface needs. Available fields depend on the uploaded file and supported checks; results keep missing evidence and unknown values explicit.
Manufacturer, family and model or variant, plus supported hardware, software, calibration and part numbers when established.
An identified, review-required or unknown outcome, with a named confidence level and a short explanation.
Condition findings, check coverage and supported checksum results, with notices for observations that need review.
Map IDs, positions and dimensions, alongside available, returned and omitted counts for the requested scan.
Rows of raw unsigned cell values, available axis values, dimensions and minimum or maximum values. Physical scaling remains unknown.
Exact changed-byte counts, differences in file length and candidate-map comparisons, including changed cells and realigned matches.
Developer setup
Set up access, try your first request, and bring the results into your own application.
Use an API or Max key with vdb_read. Request capabilities to confirm service availability, operations, file limits and retention periods.
Send the file through your backend as multipart form data. Save the returned file ID, checksum and expiry time.
Choose identification, inspection, comparison or a map scan. Send the file IDs and a unique Idempotency-Key; reuse that key for unchanged retries.
Save the returned job ID and poll its status every two seconds or slower. Stop when it completes or reaches another terminal state.
Read the compact result first. Request details for map entries or comparisons, and submit a separate grid job for a selected map's values.
Use the returned expiry times, retain any reports your workflow needs and delete uploads when finished. Re-upload expired files before starting new analysis.
ECU observation + your application
Connect analysis to your existing upload and review process. Remapdb returns structured reports while your application manages the customer request and the next action.
Upload the binary through your backend and associate its file and job IDs with your own request record. Keep API credentials on the server.
Follow background-job progress and display the completed summary. Load map, grid or comparison details when someone needs a closer look.
Use Remapdb MCP to identify, inspect or compare uploaded files through a connected assistant. Upload files through REST first; MCP works with their returned IDs.
One upload can support several operations until it expires. Keep the returned IDs with your request so your team can move from identification to inspection, maps or comparison.
API essentials
Choose identification for ECU details alone, or inspection for file condition and map candidates too. Available identifiers and confidence help your application present the result accurately.
Scan for candidate maps, inspect raw grids and compare two files. Each grid stays tied to the file and scan that produced its map ID.
Upload once, start a background job and follow its progress while your application keeps working. Retrieve the completed report using the returned job ID.
Keep building
Authentication, uploads, background jobs and retries.
Read the guideopen_in_newIdentity confidence, file condition, map grids and comparisons.
Read the guideopen_in_newCheck operations, limits and the exact response schemas.
Read the guideopen_in_newConnect uploaded files and analysis jobs to an MCP-compatible assistant.
Read the guideopen_in_newFAQ
When supported by the file evidence, it returns the ECU manufacturer, family, variant and available software, hardware, calibration or part numbers. Each report includes an identification status and confidence level. Unknown fields are omitted.
Upload raw binary files from one byte up to 8 MiB each. Convert archives, Intel HEX or S-record files to raw binary before uploading. The API does not automatically decode those formats.
No. It observes the uploaded bytes and returns a report. It does not edit maps, repair checksums, create a tuned file or confirm that a file is safe to flash.
Yes. Run a map scan, then submit its file ID, scan job ID and map ID to the map-grid endpoint. A completed job’s details contain the raw cell values and available axes, with a maximum of 65,536 cells. Physical units and scaling remain unknown.
ECU observation requires an active API or Max subscription. A key with vdb_read can use the service. Restricted integrations can use ecu_observe for submissions and ecu_read for results. The vehicle catalog trial does not include ECU observation.
Connected tools
Explore the Remapdb vehicle catalog API: vehicle search, manufacturers, models, engines and tuning data. Test the API and start with a free trial catalog.
Explore the APIExplore 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 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.