Map a diagnostic trouble code (DTC) read from an OBD-II scanner to readable diagnosis text. The /obdcodesdecoder endpoint takes the code alone — no VIN or vehicle identity required.
Who uses this API
Repair shops, telematics platforms, and warranty providers call this endpoint to turn a scanner code into plain-language diagnosis text — no VIN required.
Use cases
B2B
- Repair shops — scan-tool intake: Translate a DTC on the work order into a readable diagnosis for the advisor and technician.
- Telematics — in-vehicle alerts: Decode codes reported by a connected device so fleet or warranty dashboards show a cause, not just
P0115. - Warranty — claim context: Attach a human-readable code description when a claim is opened from a diagnostic event.
B2C
- DIY OBD apps: Let a vehicle owner look up a code from a cheap scanner and see what it means.
- Consumer mechanic apps: Show diagnosis text next to a saved vehicle after a scan.
Parameters
| Parameter | Required | Description |
|---|---|---|
code | Yes | OBD-II diagnostic trouble code, for example P0115 |
key | Yes | Your CarsXE API key |
format | No | json by default, or xml if supported by your endpoint configuration |
Example
Decode an OBD-II code
For the full interactive reference, try it live in the API Reference.
Response
- Name
success- Type
- boolean
- Description
Whether the code was decoded.
- Name
diagnosis- Type
- string
- Description
Diagnostic description for the trouble code.
- Name
date- Type
- string
- Description
Lookup timestamp or date returned by the API.
- Name
code- Type
- string
- Description
Normalized OBD code returned by the API.
Errors
See the Errors guide for the full list.
- 400 - Missing OBD code.
- 401 - API key is missing, invalid, disabled, or unauthorized.
- 404 - The code is not in the reference table, either a typo or a manufacturer-specific code.
- 429 - Usage limit exceeded.
Decode an OBD-II diagnostic trouble code into a readable diagnosis.