Vehicle data

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

Get API keys →

DIMO gives developers API access to Ford Escape 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.

The Ford Escape connects to DIMO through a DIMO device, and coverage is tested for model years 2008 and newer. DIMO gives developers API access to vehicle-state data: diagnostics, fault codes, battery and fuel health, odometer, and maintenance signals. You read that data through the Telemetry API using a Vehicle JWT for each vehicle the owner has shared with you. DIMO adds vehicle-state depth on top of GPS tracking; it doesn't replace it.

Signals by connection type

DIMO device — DIMO LTE R1 (2008 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
Diagnostic Trouble CodesobdDTCList—
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 (2012 and newer)

SignalDIMO nameUnit
OdometerpowertrainTransmissionTravelledDistancekm
Fuel PercentagepowertrainFuelSystemRelativeLevel%
Vehicle Speedspeedkm/h
Engine RPMpowertrainCombustionEngineSpeedrpm
Coolant TemperaturepowertrainCombustionEngineECT°C
Air TemperatureexteriorAirTemperature°C
Barometric PressureobdBarometricPressurekPa
Diagnostic Trouble CodesobdDTCList—
Distance Since DTC ClearobdDistanceSinceDTCClearkm
Distance with MIL OnobdDistanceWithMILkm
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 Escape 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
  • New diagnostic trouble code

Build it

Query the latest Ford Escape 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 Escape 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 Escape?

Yes. A DIMO device reports the Fuel Percentage signal (powertrainFuelSystemRelativeLevel, in %) for the Ford Escape. Query it through the Telemetry API, or use the segments query with the refuel mechanism to find where fuel level rises significantly.

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

Use a DIMO device. The record lists the DIMO LTE R1 and AutoPi for the Ford Escape. Once the owner shares the vehicle with your app, exchange your Developer JWT for a Vehicle JWT through the Token Exchange API and query the Telemetry API.

Can I get check-engine light alerts for a Ford Escape?

Yes. Both DIMO devices listed for the Ford Escape report the dtc event and the Diagnostic Trouble Codes signal. To get pushed notifications instead of polling, configure a webhook in the Vehicle Triggers API, which is in public beta.

How do I detect idling on a Ford Escape?

Use the Telemetry API segments query with the idling mechanism, which requires a DIMO device. It returns contiguous periods where engine RPM stays in the idle range, and you can set the upper bound with maxIdleRpm (default 1000).

How do I verify Ford Escape mileage?

A DIMO device reports the Odometer signal (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 Ford Escape model years work with DIMO?

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

Do I need hardware to get Ford Escape data?

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

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