External Integration API
Trackings — External Integration API
Provides access to historical vehicle tracking data within a maximum 72-hour date range. Returns a chronological array of telemetry objects for the specified vehicle.
Platform
| Base URL |
|---|
https://read.rulereld.com |
Authentication
Two headers are required for every request:
| Header | Required | Purpose |
|---|---|---|
x-api-key | Yes | API key |
provider-token | Yes | Provider authentication token |
Endpoint
GET/api/externalservice/trackings/:usdot/:vehicleId/?from={date}&to={date}
Path & Query Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
usdot | Path | Yes | Company USDOT number |
vehicleId | Path | Yes | Unique vehicle identifier |
from | Query | Yes | Start timestamp (ISO 8601) |
to | Query | Yes | End timestamp (ISO 8601) |
72-Hour LimitThe maximum query window is 72 hours. Requests spanning more than 72 hours will be rejected.
Response Structure
Returns a chronological array of telemetry objects. Each object contains the vehicle's location, speed, heading, driver, odometer reading, and timestamp.
json
[
{
"address": "string",
"coordinates": {
"lat": 0.0,
"lng": 0.0
},
"rotation": 0,
"speed": 0,
"driverId": "string",
"odometer": 0,
"date": "2026-01-10T08:32:11.000Z"
}
]Response Fields
| Field | Type | Description |
|---|---|---|
address | string | Human-readable address at the recorded location |
coordinates.lat | number | Latitude |
coordinates.lng | number | Longitude |
rotation | number | Vehicle heading in degrees |
speed | number | Speed at the recorded point |
driverId | string | Identifier of the driver at this point |
odometer | number | Odometer reading at the recorded point |
date | string | ISO 8601 timestamp of the data point |
Example cURL Request
bash
curl --location 'https://read.rulereld.com/api/externalservice/trackings/123456/<vehicleId>/?from=2026-01-10T00:00:00.000Z&to=2026-01-13T00:00:00.000Z' \
--header 'x-api-key: <your-api-key>' \
--header 'provider-token: <your-provider-token>'Data is returned in chronological order. Contact the support team for access credentials or integration assistance.