Rate limiting and retry strategies

Expert

Handle HTTP 429 responses and implement exponential backoff to build resilient Data API integrations.

What you'll learn

  • What triggers rate limiting in FileMaker Server vs. FileMaker Cloud
  • How to detect a 429 response and retry with backoff
  • How to design integrations that stay within connection limits

FileMaker Server and FileMaker Cloud impose limits on concurrent connections and request rates. When limits are reached, the server returns HTTP 429 (Too Many Requests) or rejects with a connection error. Integrations that do not handle this will drop data or fail entirely under load.

1/3
1

Sources of rate limiting

FileMaker Server has a connection license limit (simultaneous clients) and a maximum concurrent API connection count (configurable in Admin Console). FileMaker Cloud adds per-minute and per-day request quotas. Exceeding any limit returns HTTP 429 or a connection refusal.

FileMaker Cloud vs. On-Premise Data API differencesReading database and layout metadata from the Data API

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

Sign in to FM Dojo