Data API token management and session reuse

Expert

Obtain, cache, and refresh Data API tokens efficiently to minimize authentication round-trips and avoid rate limits.

What you'll learn

  • How FileMaker Data API tokens expire
  • How to cache and reuse a token across requests
  • How to detect token expiry and re-authenticate transparently

Every Data API request requires a bearer token obtained from the /sessions login endpoint. Tokens expire after 15 minutes of inactivity (configurable on FileMaker Server). Requesting a new token for every API call adds latency and consumes a server connection slot. Caching and refreshing tokens correctly is essential for production integrations.

1/3
1

Token lifetime and expiry

A token expires after a configurable idle timeout (default 15 minutes). Any authenticated API call resets the idle timer. Tokens do not have a fixed absolute expiry — they expire only after the idle period with no activity.

Executing FileMaker scripts via the Data APIFind request operators and wildcards

Sign in to track your progress and pick up where you left off.

Sign in to FM Dojo