Skip to main content

​
Base URL

​
Authentication

Every request requires a workspace API key sent via header:

​
Versioning

FileFeed uses date-based API versions, the same pattern Stripe and Twilio use. Send the version you want to pin to as a header:
If you omit the header, the API falls back to the default version pinned to your workspace (set at signup; configurable from the dashboard). Older workspaces remain on 2024-09-01 until they explicitly opt in.

​
Available versions

See the migration guide for upgrade instructions and the changelog for the full version history.

​
Response headers

Every response echoes the version the server applied:
Deprecated routes additionally include:
Watch for Deprecation: true in your integration’s response handler — that header is how you’ll know a route you depend on is going away. The @filefeed/sdk surfaces it through the onDeprecation callback automatically.

​
Pagination

  • Page-based: ?page=1&limit=50
  • Offset-based (data pages): ?offset=0&limit=1000
For a typed client, use the @filefeed/sdk API Library. The SDK pins to a specific API version per release, so an SDK upgrade is what moves you between versions — never an out-of-band wire change.