Data Extract API: keeping a downstream copy in sync

The Data Extract API (developers.rtafleet.com) returns raw rows from Fleet360 tables for use in data warehouses and integrations. This article covers how to keep a downstream copy in sync when you pull data incrementally.

How an incremental pull works

Every row in an extractable table carries an etag - a value that increments whenever any column in the row changes. When you call the extract endpoint with an etag parameter, the API returns only rows that were created or changed since that marker, sorted by etag, and hands you back a nextEtag for your next call.

What an incremental pull does not return

Incremental pulls return rows that exist and were added or changed since your marker. There is no separate deletion notice: when a row is removed from the Fleet360 table it simply never appears in a pull again. A downstream copy that is only fed by incremental pulls keeps that row forever - this is how a copy ends up with extra records that no longer exist in Fleet360.

Archived is not the same as deleted

An archived asset is still a real row - it is returned by pulls and shows in Fleet360 under the archive view, just flagged as archived. A deleted record no longer exists at all. If your downstream count is higher than Fleet360’s, do not assume the difference is archived assets: compare against a current full pull first. Rows your copy has that Fleet360 does not return at all are deleted records; rows that come back with an archive flag are archives and need different handling.

Reconcile with a periodic full pull

1. Run a full pull: call the extract endpoint with etag=0 and page through with nextEtag until it is no longer returned.

2. Remove any row from your copy whose key is not in the current result.

3. Repeat on a schedule that fits how exact your copy needs to be (weekly or monthly is typical), or whenever counts drift.