> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stigg.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Webhooks & durable queues

In addition to native connectors to third-party business applications, Stigg can notify **any application** about changes that take place on the platform in real time — customer, subscription, and entitlement changes all trigger events.

Two delivery methods are available:

## Webhooks

The default delivery method. Stigg calls an HTTP endpoint you configure with the event payload as soon as it happens.

For setup steps, the full event catalog, and payload reference, see [Webhooks](/api-and-sdks/api-reference/webhooks/introduction) in the API Reference.

## Durable queues (SQS)

For customers who need greater reliability, durability, or support for higher event volumes, Stigg can publish the same events to a dedicated, durable AWS SQS queue instead of (or alongside) webhooks.

This option is available as part of the Stigg Scale plan — contact [Stigg Support](mailto:support@stigg.io) to set it up. See [Durable queues (SQS)](/api-and-sdks/api-reference/webhooks/durable-queues) for details.


## Related topics

- [Durable queues (SQS)](/api-and-sdks/api-reference/webhooks/durable-queues.md)
- [Status APIs](/api-and-sdks/integration/upstream-apis.md)
- [I want to run Stigg Sidecar and API in production](/guides/i-want-to/run-stigg-sidecar-api-in-production.md)
- [Sidecar Failure patterns and triage](/documentation/high-availability-and-scale/sidecar/failure-patterns.md)
- [Integrations](/documentation/native-integrations/overview.md)