Overview
`code` is trimmed and uppercased, then must be a letter P, B, C or U, a digit 0-3 and three hex characters (0-9, A-F); anything else returns 400. The letter sets `system`: Powertrain, Body, Chassis or Network. Each code is one stored record rebuilt weekly from three open sources: OBDex for generic content, an OBD codes list for the warning lamp and system category, and a DTC database of carmaker titles for 32 makes.
`codeType` is `generic` when OBDex has a record for the code. Otherwise it follows SAE J2012 numbering: P1, P30-P33, B1, B2, C1, C2, U1 and U2 are manufacturer-controlled and read `manufacturer`, the rest `generic`. Where OBDex's title disagrees with the standard list (low word overlap after expanding abbreviations such as EGR and MAF), its detailed content is dropped and only the standard title kept, so the paid detail fields are null rather than describing another fault.
`warningLight` is the lamp from the category data, or Check Engine Light when OBDex marks the code as lighting the MIL. `subsystem` is the part after the dash in the category, such as Ignition. `lang=de` returns German title, description, causes and symptoms where OBDex has them, and English otherwise.
`make` accepts common spellings (Chevrolet or Chevy, VW, Mercedes or Benz) and is ignored, not rejected, when unrecognised. With a supported make, `manufacturer` carries that carmaker's title for the code; `availableMakes` lists every make that defines it, or is null. A carmaker-range code that other makes define but the given make does not returns `found: false`, with `availableMakes` still listed. Carmaker titles cover P1 powertrain codes only. With a GM brand (Chevrolet, GMC, Buick, Cadillac, Pontiac, Oldsmobile, Saturn, Geo, Hummer), C0035, C0040, C0045 and C0050 return GM's left front, right front, left rear and right rear wheel speed sensor circuit titles with the ABS Light, in place of the SAE meaning. An unknown code returns 200 with `found: false`. On the Free plan the description, causes, symptoms, components, repair, cost, labor, flags, related codes, `subsystem` and `manufacturer` are null.
Formula
One function covers the whole catalog: the first argument names the source, the next are its inputs, and the field after them says which single value lands in the cell. Formulas covers the grammar that applies to all of them.
=VERVE("dtclookup", A2, "found")=VERVE.CALL("dtclookup", A2, "found")A2 holds the code you are looking up. Drag the formula down and each row resolves on its own.
With literal values
Nothing has to come from a cell — typed values work the same way.
=VERVE("dtclookup", "P0301", "found")=VERVE.CALL("dtclookup", "P0301", "found")Inputs
Required inputs are positional, in the order below, followed by the field. Everything else is passed as a "name", value pair after that — the same shape as SUMIFS. Premium inputs are accepted on every plan but only take effect on plans that include them.
| Input | Type | Where it goes | Description |
|---|---|---|---|
codeRequired | string | argument 2 (A2) | The OBD-II trouble code: P, B, C or U followed by four characters, for example P0301, U0100 or P2BAC. A VAG (VW, Audi, SEAT, Skoda) 5-digit code in the OBD-II ranges is also accepted, for example 16684 for P0300 length 0–10 |
makeOptional | string | "make", value | The vehicle make, for carmaker-specific codes, for example Ford, Chevrolet, Audi or Lexus. Brands that share a code list answer from it, so Audi, SEAT and Skoda use the Volkswagen list and Lexus uses Toyota's length 0–40 |
langOptional | string | "lang", value | Language of the title, description, causes and symptoms of generic codesendedefault en |
Passing an option
=VERVE("dtclookup", A2, "found", "make", "Ford")=VERVE.CALL("dtclookup", A2, "found", "make", "Ford")What lands in your sheet
The field — the argument after the inputs — is what makes the formula resolve to one cell. Its value is a dot-path from the table below, so swapping it is how you pull a different value — one formula per column.
Seeing everything at once
Leave the field out and the formula returns the whole response instead: two columns, field name on the left and value on the right, spilling from the cell you typed in.
=VERVE("dtclookup", A2)=VERVE.CALL("dtclookup", A2)The second row's table would land on top of the first's, and every cell after the first reads #REF! (#SPILL! in Excel). Keep one per sheet, or name a field, and leave the cells below and to the right empty.
Response fields
Paths are relative to data. Each one is exactly what the field argument accepts, so swapping it is how you pull a different value into a cell. On a plan without a Premium field the cell reads #PREMIUM(field) rather than a value, so a locked field never looks like a real answer.
| Use as the field | Type | Example cell value | Description |
|---|---|---|---|
code | string | P0301 | The trouble code, uppercased |
found | boolean | true | Whether the code has a record; with make, a carmaker-range code counts only when that make's list defines it |
system | string | Powertrain | Vehicle system: Powertrain, Body, Chassis or Network |
subsystemPremium | string | Ignition | Powertrain subsystem, for example Ignition or Transmission |
codeType | string | generic | generic (same meaning on every vehicle) or manufacturer (carmaker-specific) |
title | string | Cylinder 1 Misfire Detected | Standard title of a generic code |
descriptionPremium | string | Misfires concentrated on cylinder 1. A cylinder-specific code points away from shared causes (fuel p… | What the code means and what the control module detected |
warningLight | string | Check Engine Light | Warning light the code turns on, for example Check Engine Light or ABS Light |
affectedComponentsPremium | array | ["ignition_coil","spark_plug","fuel_injector"] | Components involved, as identifiers such as ignition_coil |
causesPremium | array[4] | Common causes of the code | |
causes.0.causePremium | string | Ignition coil for cylinder 1 failed | The cause |
causes.0.likelihoodPremium | string | high | How often this cause is responsible: high, medium or low |
symptomsPremium | array | ["Check engine light on or flashing","Rough idle and uneven running","Power loss, hesitation under acceleration"] | Symptoms a driver may notice |
repairDifficultyPremium | string | easy | easy, medium, hard or shop_only |
diyPossiblePremium | boolean | true | Whether the usual repair is within reach of a home mechanic |
estimatedRepairCostPremium | object | {…} | Typical repair cost range |
estimatedRepairCost.minPremium | number | 40 | Low end of the cost range |
estimatedRepairCost.maxPremium | number | 800 | High end of the cost range |
estimatedRepairCost.currencyPremium | string | EUR | Currency of the cost range (EUR) |
estimatedLaborHoursPremium | object | {…} | Typical labor time range |
estimatedLaborHours.minPremium | number | 0.3 | Low end of labor hours |
estimatedLaborHours.maxPremium | number | 4 | High end of labor hours |
emissionsRelatedPremium | boolean | true | Whether the fault affects emissions |
limpModePossiblePremium | object | null | Whether the fault can put the vehicle into limp mode |
relatedCodesPremium | array | ["P0302","P0303","P0304"] | Codes that commonly appear with this one |
make | object | null | The make the lookup used, when a supported make was given |
manufacturerPremium | object | null | The carmaker's definition of a carmaker-specific code, when make is given |
availableMakes | object | null | Makes that define this carmaker-specific code |
language | string | en | Language of the returned text |
Filling a whole column
Both platforms make one batched call for a column rather than one request per cell, and both cost the same — 1 credit per row looked up. How you write it differs, because the two runtimes batch at different points.
=VERVE("dtclookup", A2:A100, "found")In Google Sheets, give the arguments ranges and the answers spill down from the cell you typed in. Custom functions there run synchronously and in isolation, so dragged cells cannot be coalesced — the range form is how a column becomes one call. The field is required here: a per-row two-column table has nowhere to spill. Use a full column per input (A2:A100, not A2) — a single-cell reference is read as row 1 only and the rest of the column comes back blank.
In Excel, type the formula once and fill down — no range form and none needed, because its runtime is asynchronous and the add-in coalesces the calls a fill produces into a single batched request. Do not hand VERVE.CALL a range: Excel flattens it into positional arguments, so A2:A100 arrives as a hundred separate arguments and the cell reads #ERR rather than filling.
Either way, column A holds your code values and the answers land beside them, one row each, blank rows skipped.
When a cell doesn't fill
A failed lookup returns readable text starting with #ERR rather than a spreadsheet error, because Excel cannot show a custom message on a real error — you would get a bare #VALUE! with no reason. The trade-off is that IFERROR() will not catch it; test with LEFT(cell, 4) = "#ERR" instead. Error handling covers the rest.
| Cell reads | What happened |
|---|---|
#ERR Not connected | No API key saved. Open the side panel and connect your account. |
#ERR Replace <name> with a cell or value | A preview formula was copied as-is. Swap the placeholder for a cell reference. |
#ERR No "x" in dtclookup | An option name this source does not take. The message lists the ones it does. |
#ERR No data point "…" | The field path is not in the response. Check it against the table above. |
#PREMIUM(field) | The field exists but your plan does not include it. |
#ERR Out of credits | The cycle's credits are spent. Usage resets on your billing date. |
Before the formula works
The add-in reads the API key you saved once in the side panel — the key never goes in the formula, so a shared sheet does not leak it and a collaborator without access simply sees the last calculated values.
- Install the add-in for Google Sheets or Excel.
- Open the side panel and sign in, or paste a key from your dashboard.
- Type the formula above into any cell.
Use cases
- Scan Tool Apps
- Bluetooth OBD-II dongle apps turn the raw codes a car reports into plain-language titles, likely causes and the warning light involved.
- Repair Shop Software
- Workshop systems attach the likely causes, labor hours and cost range to a job card the moment a technician reads a code.
- Fleet Telematics
- Fleet platforms receiving fault codes from vehicles flag which ones are emissions-related or can put the vehicle into limp mode, and route them to maintenance.
- Used Car Inspections
- Inspection and listing tools explain stored codes found during a pre-purchase check in terms a buyer understands.
Other ways to use DTC Lookup
Set up DTC Lookup on VerveSheets, or reach the same source a different way. Your VerveSheets account and credits work on all of them — one key, one balance.
Related
More in Transportation: