edge.api.stigg.io) is a separate, low-latency, REST-style JSON layer used for paywall and entitlement reads. It’s distinct from the GraphQL API (api.stigg.io) and the REST 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
GraphQL operations routed through the Edge API
The following GraphQL operations are served by the Edge API and share the limit above, instead of the per-operation limits on the GraphQL rate limits page:| SDK method | GraphQL operation |
|---|---|
| getPaywall (public) | paywall |
| getEntitlements / getEntitlement / getBooleanEntitlement / getNumericEntitlement / getMeteredEntitlement | entitlement |
| getActiveSubscriptionsList | getActiveSubscriptionsList |
Behavior
- When the limit is exceeded, Stigg returns a
429response:{"error":"rate_limit_exceeded","message":"Too many requests"} - No
Retry-Afterheader is included in the response - The
/healthendpoint is exempt from rate limiting
If higher rate limits are required, please contact Stigg Support
