API integrations · 2:03 · English
Inspect and compare ECU files with the observation API
Use the Remapdb ECU observation API to upload a binary file, request identification and follow an inspection job through to its report.
Before you start
ECU observation access and ECU files you are authorised to inspect.
Recorded in the Remapdb demonstration environment with example data. Use your own account details and review the saved result.
Put it into practice
- Upload and identify the reference file.
- Review the inspection results and candidate grids.
- Compare files and remove unused uploads.
Follow at your own pace
Video transcript
Jump to a chapter or read the walkthrough step by step.
0:00 ECU observation workflow
The ECU observation API adds file inspection and comparison to your own tools. This sample demo uses generated binary files to show the complete workflow.
0:17 Integration guide
The guide explains authentication, uploads and background jobs. Your backend supplies the API key; the capabilities response lists available operations, file limits and retention periods.
0:30 Upload the reference file
An upload returns a file identifier and checksum. Subsequent requests refer to that identifier, so the same file can be identified, inspected and compared.
0:42 Identification and job results
Identification returns a job identifier. The application checks that job, then reads its completed report. Our generated sample has unknown identity; the confidence information stays visible.
0:56 Inspect and explore maps
Inspection follows the same job workflow. Its report includes observations, region offsets and candidate maps. Returned map identifiers connect each candidate to the next request.
1:08 Read a candidate grid
The file, scan and map identifiers select a candidate grid. This table displays its returned cells and dimensions. These are raw values, with no assumed physical units.
1:20 Download map descriptors
A download link retrieves the saved candidate list. The manifest supplies the map count and checksum, ready to verify and retain in your workflow.
1:30 Compare two files
A second upload supplies the comparison file and its identifier. Both file identifiers are sent together in the comparison request. The completed report shows four changed bytes.
1:43 Retention and cleanup
Expiry values describe how long uploads and reports remain available. Save the records you need, then remove finished uploads. Bring the resulting observations into your own review interface.
Your next step
Put the walkthrough into practice
Start with the free widget, or compare plans for your website and application.



