Skip to main content
Upstream Stigg APIs are the central Stigg services that power your entitlement system. Monitor overall health and subscribe to incident updates via the Stigg Status Page via email, RSS feed or Slack. The public status page does not provide an official public API. However, the underlying metrics shown on the page can be retrieved by querying an internal endpoint, which returns data including component uptimes. Example request (last 3 months, UTC range calculated dynamically): 
curl "https://status.stigg.io/proxy/status.stigg.io/component_impacts?start_at=$(date -u -v-3m '+%Y-%m-%dT%H:%M:%SZ')&end_at=$(date -u '+%Y-%m-%dT%H:%M:%SZ')"
Example response structure: 
{
  "incident_links": [
    {
      "published_at": "2025-06-16T13:01:53.265Z",
      "id": "01JXWD9YQJFZ0BEE05XBFQD7CW",
      "name": "Increased API latency",
      "status": "resolved",
      "permalink": "https://statuspage.incident.io/stigg/incidents/01JXWD9YQJFZ0BEE05XBFQD7CW"
    }
  ],
  "component_uptimes": [
    {
      "component_id": "01JQV6ECFPKWSMXBQ81NHKKWQP",
      "data_available_since": "2024-07-08T06:58:00Z",
      "uptime": "100.00"
    },
    {
      "component_id": "01JQV6ECFP7YKP9DC886WCCD6B",
      "data_available_since": "2025-04-02T12:08:33Z",
      "uptime": "100.00"
    },
    {
      "component_id": "01JWWMF1XCHBJA90R2GBFDCPGC",
      "data_available_since": "2024-07-14T12:56:00Z",
      "uptime": "100.00"
    }
  ]
}
ComponentID
API (api.stigg.io)01JQV6ECFPKWSMXBQ81NHKKWQP
Edge API (edge.api.stigg.io)01JQV6ECFP7YKP9DC886WCCD6B
Infrastructure01JWWMF1XCHBJA90R2GBFDCPGC
App (stigg.io)01JQV6ECFPD3JFJ29DX6E31K62

​
Durable delivery via SQS

As an alternative to webhooks, Stigg provisions multiple AWS SQS queues for scenarios that require higher durability and volume handling. This approach provides more reliable delivery guarantees. Additionally, the persistent cache consumes a Stigg-managed SQS queue to keep Redis fresh and synchronized with the latest entitlement data.