Vehicle data

Ford Explorer vehicle data API: signals, model years and connection options

Get API keys →

DIMO gives developers API access to Ford Explorer vehicle data. Model years 2008 and newer connect with a DIMO device (DIMO LTE R1 or AutoPi). Headline signals include odometer, fuel percentage and vehicle speed.

DIMO gives developers API access to vehicle-state data: diagnostics, fault codes, battery and fuel health, odometer, and maintenance signals. For the Ford Explorer, data comes from a DIMO device, either the DIMO LTE R1 or AutoPi, on model years 2008 and newer. This coverage has been tested rather than expected. Once an owner shares the vehicle, use the Telemetry API with a Vehicle JWT to query the signals it reports.

Signals by connection type

DIMO device — DIMO LTE R1 (2013 and newer)

SignalDIMO nameUnit
OdometerpowertrainTransmissionTravelledDistancekm
Fuel PercentagepowertrainFuelSystemRelativeLevel%
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 TypeobdFuelTypeName—
Low Voltage BatterylowVoltageBatteryCurrentVoltagevolts
OBD Device Plugged InobdIsPluggedIn—
Powertrain TypepowertrainType—
Throttle PositionpowertrainCombustionEngineTPS%
Altitude LevelcurrentLocationAltitudem
CoordinatescurrentLocationCoordinates—
HeadingcurrentLocationHeadingdegrees

DIMO device — AutoPi (2008 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
Manifold Absolute PressureobdMAPkPa
Short Term Fuel Trim (Bank 1)obdShortTermFuelTrim1%
Throttle PositionpowertrainCombustionEngineTPS%
Warmups Since DTC ClearobdWarmupsSinceDTCClear—
Altitude LevelcurrentLocationAltitudem
CoordinatescurrentLocationCoordinates—

No factory connectivity?

Ford Explorer model years 2008 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 Ford Explorer 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 Ford Explorer signals
const data = await dimo.telemetry.query({
...vehicleJwt,
query: `
query {
signalsLatest(tokenId: ${tokenId}) {
powertrainTransmissionTravelledDistance {
value
timestamp
}
powertrainFuelSystemRelativeLevel {
value
timestamp
}
speed {
value
timestamp
}
}
}`,
});
console.log(JSON.stringify(data, null, 2));

Full walkthrough: Developer quickstart.

FAQ

Can I read fuel level remotely on a Ford Explorer?

Yes, with a DIMO device. It reports Fuel Percentage (powertrainFuelSystemRelativeLevel), which you can read through the Telemetry API using a Vehicle JWT.

How do I track a Ford Explorer with no connected services?

Use a DIMO device, either the DIMO LTE R1 or AutoPi. After 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 Ford Explorer?

Idling events come from a DIMO device. Query the Telemetry API segments resource with the idling detection mechanism, which treats periods where engine RPM stays in the idle range as segments. You can tune the upper RPM bound with maxIdleRpm, which defaults to 1000.

How do I detect harsh braking on a Ford Explorer?

Harsh braking events come from a DIMO device. You can count them per trip by adding a HarshBraking entry to eventRequests in a segments query, or have DIMO push them to your server with a Vehicle Triggers API webhook on behavior.harshBraking.

How do I verify Ford Explorer mileage?

A DIMO device reports the odometer signal. To get a verifiable record, call the Attestation API odometer-statement endpoint with a Vehicle JWT, then retrieve the resulting credential through the Telemetry API.

Which Ford Explorer model years work with DIMO?

DIMO devices have been seen working on Ford Explorer model years 2008 and newer. For older vehicles, contact DIMO for additional support.

Do I need hardware to get Ford Explorer data?

Yes. DIMO lists no OEM cloud connection for the Ford Explorer, so data comes from a DIMO device.

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