Skip to main content
The Edge API (edge.api.stigg.io) is a separate, low-latency, REST-style JSON layer used for paywall and entitlement reads. It’s distinct from the REST API (api.stigg.io) and the GraphQL API, and these limits apply whether you call it directly or through SDK operations that route through it.

​
Rate-limited endpoints

The following endpoints are subject to Edge API rate limiting:
  • /v1/a/:accountId/e/:environmentId/paywall.json
  • /v1/a/:accountId/e/:environmentId/p/:productId/paywall.json
  • /v1/a/:accountId/e/:environmentId/c/:customerId/entitlements.json
  • /v1/a/:accountId/e/:environmentId/c/:customerId/entitlements-state.json
  • /v1/a/:accountId/e/:environmentId/c/:customerId/subscriptions.json
  • /v1/a/:accountId/e/:environmentId/config/client-sdk-configuration.json
  • /v1/a/:accountId/e/:environmentId/config/server-sdk-configuration.json
  • /v1/a/:accountId/e/:environmentId/config/persistent-cache-service-configuration.json
  • /v1/a/:accountId/e/:environmentId/credentials/event-queue.json
The default rate limit is 6,000 RPM per API key, shared across all of the endpoints above (not per-endpoint), aggregated globally across all regions.

​
SDK reads routed through the Edge API

When using the Stigg SDKs (including Sidecar), reads for paywalls, entitlements, and active subscriptions — such as Get Entitlements and Check Entitlement — are served by the Edge API and share the limit above, regardless of whether your integration uses the REST or GraphQL API. If you’re using the GraphQL API directly, see the operation-level mapping.

​
Behavior

  • When the limit is exceeded, Stigg returns a 429 response: {"error":"rate_limit_exceeded","message":"Too many requests"}
  • No Retry-After header is included in the response
  • The /health endpoint is exempt from rate limiting
If higher rate limits are required, please contact Stigg Support