The feed API provides approved applications with paginated access to PureTrack live tracking data. Data is sorted by insert timestamp + batch + row number, meaning you can always pull from the last point received, without missing any data.
To implement PureTrack data as a layer for users to see in your own app, see the traffic API.
GET https://feed.puretrack.io/api/feed
Send the API key in the X-API-Key header. Send Accept: application/json with each request.
curl -H "Accept: application/json" -H "X-API-Key: your-api-key" "https://feed.puretrack.io/api/feed?start=1713590000:0:0"
next value and use it as the next request's start.unix_timestamp:batch:row_number, but it is opaque: store and resend it as a string. Do not parse, increment, or generate it. Keep the same filters while following a cursor.| Parameter | Description |
|---|---|
start | Required cursor. Use a timestamp within the previous 24 hours followed by :0:0 for an initial request, or use the exact next cursor from a previous response. Note this is the inserted timestamp, not the point timestamp. |
end | Optional inclusive cursor at which to stop. |
limit | Optional number of points to return, from 1 to 30,000. Defaults to 30,000. |
type_ids | Optional comma-separated list of object type IDs. |
source_ids | Optional comma-separated list of source type IDs. |
keys | Optional comma-separated list of tracker keys to include, for example Y-ZK-GOP,X-timbo. A maximum of 100 keys may be supplied. |
lat1, long1, lat2, long2 | Optional bounding-box corners, matching the other PureTrack APIs. Supply all four values together; their order does not matter. |
GET https://feed.puretrack.io/api/feed?start=1713590000:0:0&keys=Y-ZK-GOP,X-timbo&lat1=-37.82614&long1=175.32898&lat2=-37.78996&long2=175.29426
The data array contains compact, compressed point strings. Each string includes the tracker's point timestamp; the insert timestamp, batch, and row number are used only inside the opaque pagination cursor.
{
"data": [
"T1713592582,L-37.78174,G174.88159,A4685,C338,S144.05,O56,DC828EA,U12,EZK-MZE,KY-ZK-MZE"
],
"next": "1713592586:4:37",
"has_more": false,
"success": true,
"http_code": 200
}
To decode the data format, see the Traffic API page for details.
Stealth points are excluded. The point payload excludes names and phone numbers, unless included as the main label.