Auth0 FGA Tuple Rate Limits

Auth0 Fine-Grained Authorization (FGA) Tuple rate limits function differently from standard API rate limits. Auth0 counts each individual tuple against the rate limit rather than the number of API requests. Customers may require clarification on how Auth0 calculates Tuple rate limits to prevent rate-limiting errors.

• Auth0
• Fine-Grained Authorization (FGA)
• Rate Limits

How does Auth0 calculate Write Tuple rate limits?

Auth0 FGA calculates Tuple rate limits based on the number of tuples that are in the request, rather than the number of HTTP requests that the application makes. Review the tuple-based counting method, understand how batch requests consume the quota, and consult the documentation to determine the exact rate limit for the active subscription tier.

• Tuple-based counting: Each individual tuple inside a write/read request counts as one operation against the Write Tuple rate limit.
• Batch requests: When a single API request contains multiple tuples, Auth0 counts every tuple in that batch toward the rate limit. For example, a single request containing 10 tuples consumes 10 operations from the rate limit quota.
• Documentation: Review the FGA Subscription Plans documentation for specific rate limit quotas based on the active subscription tier.

The following Tuples payload would consume 3 RPS from the rate limit: 

{
  "writes": {
    "tuple_keys": [
      {
        "user": "user:anne",
        "relation": "reader",
        "object": "document:readme"
      },
      {
        "user": "user:bob",
        "relation": "editor",
        "object": "document:readme"
      },
      {
        "user": "user:charlie",
        "relation": "viewer",
        "object": "document:readme"
      }
    ]
  }
}