> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remapdb.com/llms.txt
> Use this file to discover all available pages before exploring further.

# DTC lookup

> Look up diagnostic trouble codes with generic and manufacturer-specific reference definitions.

DTC lookup returns definitions from Remapdb's diagnostic-code dictionary. It is included with every active **API** and **MAX** API subscription and requires the existing `vdb_read` key permission. Requests return immediately: there are no jobs, uploads or lookup credits.

Open **API → [DTC lookup](https://app.remapdb.com/api/dtc)** in the app to check subscription and key readiness and find the endpoint references. Manage credentials under **API → API Keys & Usage → [API Keys](https://app.remapdb.com/api/keys)**.

## Look up one code

```bash theme={null}
curl 'https://api.remapdb.com/v2/dtc/codes/P1000?manufacturer=FORD' \
  --header "Authorization: Bearer $REMAPDB_API_KEY"
```

```json theme={null}
{
  "code": "P1000",
  "found": true,
  "matches": [
    {
      "code": "P1000",
      "type": "P",
      "description": "Manufacturer Controlled DTC",
      "scope": "generic",
      "manufacturer": null
    },
    {
      "code": "P1000",
      "type": "P",
      "description": "OBD System Readiness Test Not Complete",
      "scope": "manufacturer",
      "manufacturer": { "name": "FORD", "id": 10691 }
    }
  ]
}
```

The same code can mean different things for different manufacturers. Use `GET /v2/dtc/manufacturers` to get supported tokens, then supply a token such as `FORD` or `AUDI`. This includes that manufacturer's definitions plus generic references. Omit the filter to see all available interpretations. Unknown manufacturer tokens return `400`.

> [!NOTE]
>
> `scope: generic` identifies the generic-reference category; it does not prove that a definition applies to every vehicle. `scope: unassigned` means the source has no confirmed manufacturer context. Definitions are reference text, sometimes including possible causes—not a diagnosis, repair instruction or proof of a faulty component. Check vehicle-specific service information before acting on a code.

Manufacturer IDs can be missing or shared by different names. Use the returned **manufacturer token**, not its numeric ID, as your filter. Definitions are returned as stored; `Accept-Language` does not translate them.

## Look up several codes

```bash theme={null}
curl 'https://api.remapdb.com/v2/dtc/lookup' \
  --header "Authorization: Bearer $REMAPDB_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{"codes":["P0300","P1000","U0001"],"manufacturer":"FORD"}'
```

The response has a `results` array with one result per input code, in the same order. Each result has `code`, `found` and `matches`. A missing code has `found: false` and `matches: []`; it does not fail the other lookups. Submit 1–20 codes per request. Codes are trimmed and uppercased; malformed codes fail the request. For a single-code URL, a valid code with no matching definition returns `404`.

## Search and browse

```bash theme={null}
curl 'https://api.remapdb.com/v2/dtc/codes?query=misfire&limit=20' \
  --header "Authorization: Bearer $REMAPDB_API_KEY"
```

| Parameter | Use |
| - | - |
| `query` | Code prefix such as `P03` (2–5 characters), or a description substring such as `misfire` (3–100 bytes). Omit to browse. |
| `manufacturer` | Exact token from the manufacturer list; case-insensitive. |
| `type` | `P` powertrain, `B` body, `C` chassis or `U` network. |
| `scope` | `generic`, `manufacturer` or `unassigned`. |
| `limit` | 1–100 definitions per response; default 20. |
| `offset` | Start position; default 0, maximum 100000. |

Search returns `items`, `total` and `pagination`. `total` counts matching definitions, not distinct codes. Results sort by code and manufacturer. Follow `pagination.next_offset` while `pagination.has_more` is true. Search is case-insensitive; `%` and `_` are literal characters, not wildcards. Filters are combined, so an incompatible filter combination returns an empty list.

## Errors and limits

Responses use `{ "error": { "code": "invalid_request", "message": "..." } }` on failure. `401` means invalid credentials; `403` means missing permission or an inactive/ineligible subscription. Invalid codes, filters or fields return `400`. Batch requests require JSON (`415` otherwise) and must stay within 64 KiB (`413` if exceeded). The shared API-key rate limit applies (`429`); no DTC-specific quota is added. A temporarily unavailable dictionary returns `503`.

## Use through MCP

The same data is available through `lookup_dtc`, `lookup_dtc_codes`, `search_dtc_codes` and `list_dtc_manufacturers`. No separate DTC permission or package configuration is required. For example, ask your connected assistant: “Look up P1000 for Ford and show generic and manufacturer-specific meanings separately.”

See [AI integrations](https://docs.remapdb.com/api/ai-integrations.md) for connection setup. The [API reference](https://docs.remapdb.com/api/api-reference.md) includes all four DTC operations and their response schemas.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.