DIMO gives developers API access to Toyota Camry vehicle data. Model years 2007 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 Camry, a combustion-engine vehicle, that data comes through a DIMO device on 2007 and newer model years. Coverage for this model is tested, not just expected. The signals, events and code example below show what the API returns for it.
Signals by connection type
DIMO device — DIMO LTE R1 (2007 and newer)
| Signal | DIMO name | Unit |
|---|---|---|
| Odometer | powertrainTransmissionTravelledDistance | km |
| Vehicle Speed | speed | km/h |
| Vehicle Ignition Status | isIgnitionOn | — |
| Engine RPM | powertrainCombustionEngineSpeed | rpm |
| Coolant Temperature | powertrainCombustionEngineECT | °C |
| Air Temperature | exteriorAirTemperature | °C |
| Distance with MIL On | obdDistanceWithMIL | km |
| DTC Count | obdStatusDTCCount | — |
| Engine runtime | obdRunTime | seconds |
| Fuel Level | powertrainFuelSystemAbsoluteLevel | liters |
| Fuel Type | obdFuelTypeName | — |
| Low Voltage Battery | lowVoltageBatteryCurrentVoltage | volts |
| OBD Device Plugged In | obdIsPluggedIn | — |
| Powertrain Type | powertrainType | — |
| Throttle Position | powertrainCombustionEngineTPS | % |
| Altitude Level | currentLocationAltitude | m |
| Coordinates | currentLocationCoordinates | — |
| Heading | currentLocationHeading | degrees |
DIMO device — AutoPi (2007 and newer)
| Signal | DIMO name | Unit |
|---|---|---|
| Odometer | powertrainTransmissionTravelledDistance | km |
| Vehicle Speed | speed | km/h |
| Engine RPM | powertrainCombustionEngineSpeed | rpm |
| Coolant Temperature | powertrainCombustionEngineECT | °C |
| Air Temperature | exteriorAirTemperature | °C |
| Barometric Pressure | obdBarometricPressure | kPa |
| Distance Since DTC Clear | obdDistanceSinceDTCClear | km |
| Distance with MIL On | obdDistanceWithMIL | km |
| Engine Air Intake | powertrainCombustionEngineMAF | grams/second |
| Engine Load | obdEngineLoad | % |
| Engine runtime | obdRunTime | seconds |
| Intake temperature | obdIntakeTemp | °C |
| Long Term Fuel Trim (Bank 1) | obdLongTermFuelTrim1 | % |
| Low Voltage Battery | lowVoltageBatteryCurrentVoltage | volts |
| Powertrain Type | powertrainType | — |
| Short Term Fuel Trim (Bank 1) | obdShortTermFuelTrim1 | % |
| Supported Fuel Types | powertrainFuelSystemSupportedFuelTypes | — |
| Throttle Position | powertrainCombustionEngineTPS | % |
| Warmups Since DTC Clear | obdWarmupsSinceDTCClear | — |
| Altitude Level | currentLocationAltitude | m |
| Coordinates | currentLocationCoordinates | — |
No factory connectivity?
Toyota Camry model years 2007 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 Camry 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 Camry signalsconst 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 Camry?
Yes, with a DIMO device. It reports Fuel Level (powertrainFuelSystemAbsoluteLevel) in liters. Once the owner shares the vehicle with you, exchange your Developer JWT for a Vehicle JWT and query the signal through the Telemetry API.
How do I track a Toyota Camry with no connected services?
Use a DIMO device. It supplies the Camry's signals, such as odometer, speed, engine RPM and coolant temperature, without any manufacturer connected services. After the owner shares the vehicle, you read the data through the Telemetry API.
How do I detect idling on a Toyota Camry?
Idling is an event listed for the Camry's DIMO device coverage. Query the Telemetry API segments resource with the idling detection mechanism, which requires a DIMO device. Idle periods are contiguous stretches where engine RPM stays in the idle range (default maximum 1000 RPM, adjustable with maxIdleRpm).
How do I detect harsh braking on a Toyota Camry?
Harsh braking is listed as an event for the DIMO LTE R1 device on the Camry. Create a webhook through the Vehicle Triggers API with the events service and the metric behavior.harshBraking, then subscribe the vehicle to it. You can also request HarshBraking event counts per trip segment through the segments resource.
How do I verify Toyota Camry mileage?
The Camry's DIMO device reports Odometer (powertrainTransmissionTravelledDistance) in km. To get verifiable proof, call the Attestation API odometer-statement endpoint with a Vehicle JWT, then retrieve the resulting credential through the Telemetry API.
Which Toyota Camry model years work with DIMO?
DIMO devices have been seen working on Toyota Camry model years 2007 and newer. For older vehicles, contact DIMO for additional support.
Do I need hardware to get Toyota Camry data?
Yes. DIMO lists no OEM cloud connection for the Toyota Camry, so data comes from a DIMO device.
Source: DIMO vehicle compatibility records. Coverage tested on a connected vehicle. Last verified .