Find the definition
Look up a code directly or search by a code prefix or description. Return structured reference text to your users.
DTC lookup API
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.
Look up a code directly or search by a code prefix or description. Return structured reference text to your users.
Filter by manufacturer and see its definitions alongside generic references, with each source category clearly marked.
Submit up to 20 codes in one request. Results follow the input order, including a separate outcome for each code.
Explore it yourself
Try an example or enter your own details. See the API’s results, explore the full JSON, and use the request in your integration.
API possibilities
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.
Open a code from your scan view and show its available definitions, keeping generic and manufacturer-specific entries clearly identified.
Accept a list of codes recorded during intake and retrieve up to 20 in one request, with a separate outcome for each entry.
Give staff a searchable reference for code meanings and manufacturer context while they review a customer's reported issue.
Build a dictionary view with description search, code prefixes and manufacturer filters. Let users browse powertrain, body, chassis or network entries.
Endpoint guide
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.
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.
GET https://api.remapdb.com/v2/dtc/codes/P1000?manufacturer=FORDSend 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.
POST https://api.remapdb.com/v2/dtc/lookup
Content-Type: application/json
{
"codes": ["P0300", "P1000", "U0001"],
"manufacturer": "FORD"
}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.
GET https://api.remapdb.com/v2/dtc/codes?query=misfire&type=P&limit=20&offset=0Retrieve 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.
GET https://api.remapdb.com/v2/dtc/manufacturersData coverage
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.
A normalized diagnostic code and its stored reference description. Text is returned in its existing language without automatic translation.
Filter powertrain (P), body (B), chassis (C) and network (U) entries using the code type returned with each definition.
Identify entries in the generic source category. This label describes the reference category, not universal applicability to every vehicle.
See the manufacturer name alongside its definition. A manufacturer filter returns that maker's entries together with generic references.
Keep entries without confirmed manufacturer context distinct. They remain searchable through the unassigned scope filter.
Retrieve supported filter tokens, available catalog IDs and definition counts. Use tokens in requests because IDs may be missing or shared.
Developer setup
Set up access, try your first request, and bring the results into your own application.
Use a key with vdb_read on an active API or Max plan. Authenticate each request with a Bearer token.
Request the supported manufacturer list and use its tokens in your selector. Omit the filter when you want all available interpretations.
Look up one code for a detail view, submit up to 20 for a scan summary, or search by code prefix and description.
Display the returned text with its generic, manufacturer-specific or unassigned scope. Preserve separate meanings when a code has multiple matches.
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.
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
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.
Send authenticated requests from your server and pass the returned definitions to your interface. There are no file uploads or background jobs to coordinate.
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.
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
One code can return several definitions. Keep generic references, manufacturer-specific entries and unassigned definitions separate so users can see the manufacturer context of each result.
Use a single-code request for a detail view, or submit up to 20 codes together for a scan summary with a separate result for each code.
Find definitions by code prefix or description, then narrow the results by manufacturer, code type and scope. Omit the query parameter to browse the dictionary.
Keep building
Requests, manufacturer context, batches and search filters.
Read the guideopen_in_newParameters, response fields and errors for a code lookup.
Read the guideopen_in_newDescription search, code prefixes and paginated results.
Read the guideopen_in_newSend several codes and handle each result independently.
Read the guideopen_in_newFAQ
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.
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.
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.
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.
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.
Connected tools
Explore the Remapdb vehicle catalog API: vehicle search, manufacturers, models, engines and tuning data. Test the API and start with a free trial catalog.
Explore the APIExplore the UK vehicle lookup API from Remapdb. Find vehicle details and estimated tuning gains by number plate, with free test registrations and a shared lookup balance.
Explore the APIExplore the Remapdb ECU observation API: ECU identification, binary inspection, map candidates, raw grids and file comparison. Analyze a file in the playground.
Explore the APIConnect your AI assistant to Remapdb’s vehicle data and API tools through MCP.
Your application. Remapdb data.
Start with an account, choose the access your project needs, and connect your own workflow.
Questions about your use case? Talk to our team.