All Stigg REST SDKs now route requests through edge.api.stigg.io by default, improving latency while keeping your existing integrations unchanged.

✨ What's New

REST SDKs now send requests through edge.api.stigg.io, which transparently proxies requests to api.stigg.io.

For supported endpoints, requests are served directly from the Edge, reducing latency without requiring any changes to your application or SDK configuration.

The following endpoints are currently served directly from the Edge:

• GET /api/v1/customers/{customerId}/entitlements/check
• GET /api/v1/customers/{customerId}/entitlements

⭐️ Why It Matters

Entitlement checks sit directly on your application's request path. Every millisecond saved on an entitlement check translates directly to a faster, more responsive app for your users.

• Zero-config performance: Lower latency out of the box without needing to configure custom routing, edge nodes, or caching layers.
• 100% backward compatible: You don't need to update API base URLs, implement custom proxy logic, or change how you instantiate Stigg SDK clients.
• Global low latency: Entitlements are evaluated closer to where your traffic originates.

📦 Availability

The Edge routing is available in the following REST SDK versions (or later):

• TypeScript: v0.1.0-beta.34
• Python: v0.1.0-beta.30
• Go: v0.1.0-beta.31
• Java: v0.1.0-beta.29
• Ruby: v0.1.0-beta.33

Simply upgrade your SDK dependency to the latest version to automatically benefit from Edge routing.