Changelog
What changed in the Customer Data API, newest first.
We version the contract conservatively: fields are added, never
removed or retyped, within /api/v1. Anything breaking would ship as
a new version path with a migration window — and an email to every
integration contact first.
2026-09-10 — v1.2.0
- Rate limiting — the per-key window is now a clock minute that
resets on the minute boundary, rather than a rolling 60-second span.
Admission is decided atomically, so the cap holds under concurrent
requests. What that means for a client:
X-RateLimit-Resetnames the exact instant your full allowance returns; refused requests still never consume quota; and a burst that spans a minute boundary can be admitted up to twice your cap in a short span — pace againstX-RateLimit-Remainingrather than assuming a smooth rate. See Rate limits. No request or response field changed. - OpenAPI document — the
X-RateLimit-RemainingandX-RateLimit-Resetheader descriptions now describe the clock-minute window.
2026-07-15 — v1.1.0
GET /api/v1/loads— addedcreatedAt(ISO 8601) to every load row: when the load was first created in FR8 Factory. Guaranteed non-null, so it's safe to key filters on. For loads that predate your data feed, this is the date the load was first imported, which may be later than the load's real-world creation. Additive only — no existing field changed.
2026-07-10 — v1 launch
GET /api/v1/loads— initial release: Bearer-key auth,updatedSincedelta polling, page-number pagination (default and max 100), a trailing 12-month window (loads scheduled to pick up in the last 12 months), per-key rate limiting (default 10/min) withX-RateLimit-*headers.- OpenAPI 3.1 document published at
/api/v1/openapi.json. - This documentation site.