Skip to Content
FR8 Factory Docs

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-Reset names 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 against X-RateLimit-Remaining rather than assuming a smooth rate. See Rate limits. No request or response field changed.
  • OpenAPI document — the X-RateLimit-Remaining and X-RateLimit-Reset header descriptions now describe the clock-minute window.

2026-07-15 — v1.1.0

  • GET /api/v1/loads — added createdAt (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, updatedSince delta 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) with X-RateLimit-* headers.
  • OpenAPI 3.1 document published at /api/v1/openapi.json.
  • This documentation site.

On this page

Help

How do I get API access?

API keys are issued per customer by the FR8 Factory team. Ask your account contact — or send us a request through the Help desk tab with your company name and use case.

How do I authenticate requests?

Send your API key in the Authorization header on every request. Keys are secret — never ship them in browser code or mobile apps.

Open the guide — How do I authenticate requests?

How do I keep my copy of the data in sync?

Use delta polling: request only records changed since your last sync cursor instead of re-downloading everything. The guide covers cursors, ordering, and replay safety.

Open the guide — How do I keep my copy of the data in sync?

What are the rate limits?

Limits are per API key and documented on the rate-limits page, along with the response headers that tell you where you stand and how to back off.

Open the guide — What are the rate limits?

What does each load field mean?

The load field dictionary defines every field the API returns — types, nullability, and freight-domain meaning (pick vs drop dates, AR, equipment types).

Open the guide — What does each load field mean?

Found a bug or missing data?

Send it through the Help desk tab with the request you made and what you expected back. You'll get a reference code, and we'll email you when it's resolved.