All endpoints require HMAC-SHA256 authentication. Generate API keys from the admin dashboard.
Every request to /api/v1/* must include three headers:
/api/v1/transponder/decodeSubmit a hex-encoded binary dump for full transponder analysis. Returns chip identification, memory mapping, ISK extraction, clone readiness assessment, and decoded fields.
| Field | Type | Required | Description |
|---|---|---|---|
| hexContent | string | Hex-encoded binary content of the transponder dump | |
| fileName | string | — | Original filename (helps with chip detection heuristics) |
| chipFamily | string | — | Hint: PCF7953, NCF29A1, PCF7945, etc. |
Chip identification, memory regions, ISK if found, clone readiness score, decoded EEPROM/EROM fields.
/api/v1/transponder/analyseRun static analysis on a hex dump — entropy measurement, crypto detection, string extraction, chip fingerprinting.
| Field | Type | Required | Description |
|---|---|---|---|
| hexContent | string | Hex-encoded binary content | |
| fileName | string | — | Original filename |
Entropy scores, detected crypto patterns, extracted strings, chip family fingerprint matches.
/api/v1/decoder/rulesRetrieve active local decoder rules. These are pattern-matching rules learned from previous decodes — VIN offsets, ISK patterns, hex signatures, CRC checks.
Array of active decoder rules with kind, pattern, confidence, and hit count.
/api/v1/decoder/rulesAdd a new decoder rule to the pattern engine. Rules are automatically applied to future decodes.
| Field | Type | Required | Description |
|---|---|---|---|
| kind | string | Rule type: vin_offset, isk_offset, hex_signature, part_number, byte_pattern, crc_check | |
| pattern | string | The match pattern (regex for hex_signature, offset spec for vin_offset/isk_offset) | |
| fileKind | string | — | Restrict to file kind: eeprom, erom, full, flash |
| extractAs | string | — | Label for extracted data: vin, isk, part_number, etc. |
| notes | string | — | Human-readable notes about this rule |
Created rule object with ID.
/api/v1/mcu/pcf7953Retrieve PCF7953 doctrine data — memory maps, programming procedures, security regions.
PCF7953 doctrine object with memory layout, security zones, programming protocols.
/api/v1/healthNo auth required. Returns service status, capabilities list, supported chips, and live data counts. Other Lock50 services poll this to discover what's available.
Service status, version, capabilities array, supported chips, data counts per table.
/api/v1/lookupBrain-to-brain query: given a brand/model/chipFamily, returns everything the transponder service knows — chip mappings, ECU dump references, EEPROM specs, immo PIN locations, transponder files, and active decoder rules.
| Field | Type | Required | Description |
|---|---|---|---|
| brand | string | — | Vehicle brand: BMW, Jaguar, Land Rover, Audi, etc. |
| model | string | — | Model name or partial match: E90, XF, Evoque |
| chipFamily | string | — | Chip family: PCF7953, NCF29A1, PCF7945 |
Transponder catalogue matches, ECU dumps, EEPROM chip specs, immo PIN locations, transponder files, active decoder rules.
/api/v1/catalogueQuery any of the 4 reference data tables directly. Filter by brand, chipFamily, with pagination.
| Field | Type | Required | Description |
|---|---|---|---|
| table | string | Table to query: transponder, ecu, eeprom, immo | |
| brand | string | — | Filter by brand |
| chipFamily | string | — | Filter by chip family |
| limit | number | — | Max results (default 100, max 500) |
Array of matching catalogue entries.