DTC lookup API

DTC lookup API for diagnostic code definitions

The Remapdb DTC lookup API returns diagnostic trouble code definitions in JSON. Look up one code or up to 20 together, search descriptions, and keep generic and manufacturer-specific meanings clearly identified in your application.

Included with active API and Max plans.

Results
Immediate JSON response
Batch size
Up to 20 codes

Explore it yourself

DTC lookup API playground

Try an example or enter your own details. See the API’s results, explore the full JSON, and use the request in your integration.

Look up a diagnostic code

Live API

Enter a code or search its description. Choose a manufacturer to see its definitions alongside generic references.

Try an example

For several codes, separate them with commas. Search examples: P03 or misfire.

Optional. Use a supported name such as FORD or AUDI.

API possibilities

Add code definitions to the tools you already use

Bring DTC reference text into your own interface, with the manufacturer context beside each definition. Your team controls how the information supports the wider diagnostic workflow.

Diagnostic dashboards

Open a code from your scan view and show its available definitions, keeping generic and manufacturer-specific entries clearly identified.

Workshop intake

Accept a list of codes recorded during intake and retrieve up to 20 in one request, with a separate outcome for each entry.

Support and dealer portals

Give staff a searchable reference for code meanings and manufacturer context while they review a customer's reported issue.

Searchable reference tools

Build a dictionary view with description search, code prefixes and manufacturer filters. Let users browse powertrain, body, chassis or network entries.

Endpoint guide

The requests behind your integration

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.

Look up a diagnostic code

Retrieve the available meanings for one code. Add a manufacturer token to include its definitions and generic references, or omit it to see all interpretations.

Example: Look up P1000 for Ford and show generic and Ford-specific meanings separately.

Endpoint
GET https://api.remapdb.com/v2/dtc/codes/P1000?manufacturer=FORD

Check several codes together

Send 1–20 codes in one JSON request. Results preserve input order and duplicates; a missing match is marked found: false without removing other results.

Example: Add definitions to P0300, P1000 and U0001 from the same Ford scan summary.

Endpoint
POST https://api.remapdb.com/v2/dtc/lookup
Content-Type: application/json

{
  "codes": ["P0300", "P1000", "U0001"],
  "manufacturer": "FORD"
}

Search and browse definitions

Search a code prefix or description and combine manufacturer, type and scope filters. Leave out query to browse; use limit and offset to paginate definitions.

Example: Find powertrain descriptions containing “misfire”, with 20 definitions per page.

Endpoint
GET https://api.remapdb.com/v2/dtc/codes?query=misfire&type=P&limit=20&offset=0

List supported manufacturers

Retrieve manufacturer tokens and their definition counts for your filters. Tokens are the request values; optional numeric catalog IDs are only supporting context.

Example: Populate a manufacturer selector with the names supported by the DTC dictionary.

Endpoint
GET https://api.remapdb.com/v2/dtc/manufacturers

Data coverage

The definition, its scope and its manufacturer

Retrieve stored DTC reference text with the fields needed to present it clearly. Coverage comes from the dictionary; a code can have several definitions or no matching entry.

Code and description

A normalized diagnostic code and its stored reference description. Text is returned in its existing language without automatic translation.

Four code families

Filter powertrain (P), body (B), chassis (C) and network (U) entries using the code type returned with each definition.

Generic references

Identify entries in the generic source category. This label describes the reference category, not universal applicability to every vehicle.

Manufacturer-specific meanings

See the manufacturer name alongside its definition. A manufacturer filter returns that maker's entries together with generic references.

Unassigned definitions

Keep entries without confirmed manufacturer context distinct. They remain searchable through the unassigned scope filter.

Manufacturer directory

Retrieve supported filter tokens, available catalog IDs and definition counts. Use tokens in requests because IDs may be missing or shared.

Developer setup

From API access to your first integration

Set up access, try your first request, and bring the results into your own application.

1

Connect your API key

Use a key with vdb_read on an active API or Max plan. Authenticate each request with a Bearer token.

2

Load manufacturer choices

Request the supported manufacturer list and use its tokens in your selector. Omit the filter when you want all available interpretations.

3

Choose the request

Look up one code for a detail view, submit up to 20 for a scan summary, or search by code prefix and description.

4

Show each definition

Display the returned text with its generic, manufacturer-specific or unassigned scope. Preserve separate meanings when a code has multiple matches.

5

Handle misses and limits

Keep successful batch entries when another code has no match. Handle single-code 404 responses and slow requests when the shared rate limit is reached.

6

Add search and browsing

Combine manufacturer, type and scope filters, then follow pagination.next_offset while pagination.has_more is true. Request only the page your interface needs.

DTC reference + your application

The code stays in context throughout your workflow

Use the same reference information in your product, internal tools and supported AI clients. A small set of synchronous endpoints handles lookup, search and manufacturer selection.

Connect your backend

Send authenticated requests from your server and pass the returned definitions to your interface. There are no file uploads or background jobs to coordinate.

Show the right context

Pair each description with its scope and manufacturer. Build manufacturer filters from the returned tokens and keep multiple definitions visible when a code has several meanings.

Use the same data through AI

Connect Remapdb MCP to look up one code, check a batch, search descriptions or list manufacturers from a supported assistant, using the same API access.

REST and MCP use the same dictionary and API access. DTC requests return immediately.

API essentials

Know what to expect

FAQ

Questions about DTC lookup API

Which plans include the DTC lookup API?

DTC lookup is included with active API and Max subscriptions and uses the vdb_read key permission. The vehicle catalog trial does not include DTC lookup.

Why can a code return more than one definition?

The same diagnostic code can have different meanings for different manufacturers. Results include scope and manufacturer information. A manufacturer filter includes that manufacturer’s definitions plus generic references.

Can I look up several diagnostic codes at once?

Yes. Send 1–20 codes to POST /v2/dtc/lookup. Results retain your input order and duplicates. A missing definition is marked found: false without failing the other results.

Can I search by description instead of a code?

Yes. Use a description query of 3–100 bytes, or a code prefix of 2–5 characters. Combine it with manufacturer, type and scope filters. Responses are paginated and can include up to 100 definitions per page.

Can I use DTC lookup through AI integrations?

Yes. The Remapdb MCP tools include lookup_dtc, lookup_dtc_codes, search_dtc_codes and list_dtc_manufacturers. They use the same subscription access and vdb_read permission as the API.

Your application. Remapdb data.

Build your next integration

Start with an account, choose the access your project needs, and connect your own workflow.