stigg-webhooks
Stigg Webhooks — Receive and Handle Events
Stigg notifies your app about changes via webhooks: subscription lifecycle, trial transitions, credit balance thresholds, auto-recharge attempts, entitlement-usage exceeded, and more. This skill covers receiving them — registering the endpoint, verifying authenticity, handling retries, and the payload envelope.
Before You Start
Per the umbrella stigg skill: search first. Webhook event names and payloads evolve. Use the Mintlify Stigg docs MCP — query_docs_filesystem_stigg against /documentation/native-integrations/webhooks/events.mdx and the per-event reference pages — to confirm the exact payload schema before authoring handler code.
Registering a Webhook
In the Stigg app: Settings → Integrations → Webhooks → + New webhook.
| Field | Notes |
|---|---|
| Service name | Human-friendly label (e.g. "Production webhooks", "Dev"). |
| Endpoint URL | Your handler — e.g. https://yourapp.com/api/stigg/webhooks. Must respond 2XX within 30 seconds or Stigg retries. |
| Events to send | Pick from the catalog (subscription, trial, credits, entitlement, customer, etc.). |
Created webhooks activate immediately. Use Send test event (⋮ menu on a specific event) to verify your handler before wiring real events.