Vehicle data

Toyota 4Runner vehicle data API: signals, model years and connection options

Get API keys →

DIMO gives developers API access to Toyota 4Runner vehicle data. Model years 2010 and newer connect with a DIMO device (DIMO LTE R1 or AutoPi). Headline signals include odometer, vehicle speed and vehicle ignition status.

DIMO gives developers API access to vehicle-state data: diagnostics, fault codes, battery and fuel health, odometer, and maintenance signals. For the Toyota 4Runner, 2010 and newer model years connect through a DIMO device, either the DIMO LTE R1 or AutoPi, and this coverage has been tested. Vehicle owners consent to and control sharing, so builders get data with clear provenance. You read the data through the Telemetry API with a Vehicle JWT.

Signals by connection type

DIMO device — DIMO LTE R1 (2013 and newer)

SignalDIMO nameUnit
OdometerpowertrainTransmissionTravelledDistancekm
Vehicle Speedspeedkm/h
Vehicle Ignition StatusisIgnitionOn—
Engine RPMpowertrainCombustionEngineSpeedrpm
Coolant TemperaturepowertrainCombustionEngineECT°C
Air TemperatureexteriorAirTemperature°C
Back Left WheelchassisAxleRow2WheelLeftTirePressurekPa
Back Right WheelchassisAxleRow2WheelRightTirePressurekPa
Distance with MIL OnobdDistanceWithMILkm
DTC CountobdStatusDTCCount—
Engine runtimeobdRunTimeseconds
Front Left WheelchassisAxleRow1WheelLeftTirePressurekPa
Front Right WheelchassisAxleRow1WheelRightTirePressurekPa
Fuel LevelpowertrainFuelSystemAbsoluteLevelliters
Fuel TypeobdFuelTypeName—
Low Voltage BatterylowVoltageBatteryCurrentVoltagevolts
OBD Device Plugged InobdIsPluggedIn—
Powertrain TypepowertrainType—
Throttle PositionpowertrainCombustionEngineTPS%
Altitude LevelcurrentLocationAltitudem
CoordinatescurrentLocationCoordinates—
HeadingcurrentLocationHeadingdegrees

DIMO device — AutoPi (2010 and newer)

SignalDIMO nameUnit
OdometerpowertrainTransmissionTravelledDistancekm
Fuel PercentagepowertrainFuelSystemRelativeLevel%
Vehicle Speedspeedkm/h
Engine RPMpowertrainCombustionEngineSpeedrpm
Coolant TemperaturepowertrainCombustionEngineECT°C
Air TemperatureexteriorAirTemperature°C
Barometric PressureobdBarometricPressurekPa
Distance Since DTC ClearobdDistanceSinceDTCClearkm
Distance with MIL OnobdDistanceWithMILkm
Engine Air IntakepowertrainCombustionEngineMAFgrams/second
Engine LoadobdEngineLoad%
Engine runtimeobdRunTimeseconds
Intake temperatureobdIntakeTemp°C
Long Term Fuel Trim (Bank 1)obdLongTermFuelTrim1%
Low Voltage BatterylowVoltageBatteryCurrentVoltagevolts
Powertrain TypepowertrainType—
Short Term Fuel Trim (Bank 1)obdShortTermFuelTrim1%
Supported Fuel TypespowertrainFuelSystemSupportedFuelTypes—
Throttle PositionpowertrainCombustionEngineTPS%
Warmups Since DTC ClearobdWarmupsSinceDTCClear—
Altitude LevelcurrentLocationAltitudem
CoordinatescurrentLocationCoordinates—

No factory connectivity?

Toyota 4Runner model years 2010 and newer have no OEM cloud connection listed. For these years, a DIMO device (DIMO LTE R1 or AutoPi) plugs into the OBD-II port and streams vehicle signals once the owner connects it and consents to sharing.

See the developer quickstart for how owners connect vehicles and grant access.

Events available

  • Idling
  • Refuel
  • Harsh braking

Build it

Query the latest Toyota 4Runner signals with the DIMO TypeScript SDK. The vehicle owner must first share access with your app through DIMO Connect.

import { DIMO } from '@dimo-network/data-sdk';
const dimo = new DIMO('Production');
const tokenId = Number(process.env.DIMO_TOKEN_ID); // from DIMO Connect
const developerJwt = await dimo.auth.getDeveloperJwt({
client_id: process.env.DIMO_CLIENT_ID,
domain: process.env.DIMO_REDIRECT_URI,
private_key: process.env.DIMO_API_KEY,
});
const vehicleJwt = await dimo.tokenexchange.getVehicleJwt({
...developerJwt,
tokenId,
});
// Latest Toyota 4Runner signals
const data = await dimo.telemetry.query({
...vehicleJwt,
query: `
query {
signalsLatest(tokenId: ${tokenId}) {
powertrainTransmissionTravelledDistance {
value
timestamp
}
speed {
value
timestamp
}
isIgnitionOn {
value
timestamp
}
}
}`,
});
console.log(JSON.stringify(data, null, 2));

Full walkthrough: Developer quickstart.

FAQ

Can I read fuel level remotely on a Toyota 4Runner?

Yes, through a DIMO device. The DIMO LTE R1 reports fuel level in liters and AutoPi reports fuel percentage. Query either one through the Telemetry API GraphQL endpoint with a Vehicle JWT.

How do I track a Toyota 4Runner with no connected services?

Use a DIMO device, either the DIMO LTE R1 or AutoPi. Once the owner shares the vehicle with your Developer License, exchange your Developer JWT for a Vehicle JWT through the Token Exchange API and query the Telemetry API.

How do I detect idling on a Toyota 4Runner?

Both the DIMO LTE R1 and AutoPi list the idling event. Query the Telemetry API `segments` resource with the `idling` detection mechanism, which requires a DIMO device. Idle segments are contiguous periods where engine RPM stays in the idle range, and `maxIdleRpm` defaults to 1000.

How do I verify Toyota 4Runner mileage?

Both DIMO device types report the odometer signal. To get verifiable proof, call the Attestation API odometer-statement endpoint with a Vehicle JWT. Then retrieve the resulting `rawVC` through the Telemetry API.

How do I detect harsh braking on a Toyota 4Runner?

The DIMO LTE R1 lists the harsh braking event. Request a `HarshBraking` count per trip with `eventRequests` in the `segments` query, or set up a webhook on `behavior.harshBraking` through the Vehicle Triggers API. The AutoPi entry lists only idling and refuel.

Which Toyota 4Runner model years work with DIMO?

DIMO devices have been seen working on Toyota 4Runner model years 2010 and newer. For older vehicles, contact DIMO for additional support.

Do I need hardware to get Toyota 4Runner data?

Yes. DIMO lists no OEM cloud connection for the Toyota 4Runner, so data comes from a DIMO device.

Source: DIMO vehicle compatibility records. Coverage tested on a connected vehicle. Last verified .