Sentry can send HTTP POST requests to any URL you control whenever something happens—a new issue is created, an error fires an alert, an issue is resolved, and more. There are two ways to set this up: Service Hooks for simple project-level notifications, and Sentry App webhooks for richer, event-driven integrations built on the Integration Platform.Documentation Index
Fetch the complete documentation index at: https://sentrydocs.dev/llms.txt
Use this file to discover all available pages before exploring further.
Service Hooks
Service Hooks are the simplest way to receive Sentry notifications over HTTP. You configure a URL and a set of events, and Sentry sends a signed POST request to that URL whenever those events occur in a project.Available events
| Event | When it fires |
|---|---|
event.alert | An alert rule fires for an event |
event.created | A new event is received and processed |
Create a Service Hook
Enable Service Hooks for the project
Service Hooks require the
servicehooks feature to be enabled for your project. Contact your Sentry administrator if you do not see the option below.Add a hook
Click Add a new hook, enter your endpoint URL, and select the events you want to receive.
Create a Service Hook via API
You can also create Service Hooks programmatically using the Sentry API.secret you use to verify incoming requests:
Webhook payload
Sentry sends a JSON payload via HTTP POST to your endpoint. The exact structure depends on the event type, but every payload includes the event data in the request body.Example event.alert payload
Verify webhook signatures
Sentry signs every webhook request using HMAC-SHA256 with the hook’s secret. You should verify this signature before processing the payload to confirm the request came from Sentry. The signature is in theX-Sentry-Hook-Signature request header.
- Python
- Node.js
Sentry App webhooks
If you need richer webhook events—beyondevent.alert and event.created—build a Sentry App using the Integration Platform. Sentry App webhooks support a much broader set of events:
| Resource | Events |
|---|---|
issue | issue.created, issue.resolved, issue.ignored, issue.assigned, issue.unresolved |
error | error.created |
comment | comment.created, comment.updated, comment.deleted |
installation | installation.created, installation.deleted |
metric_alert | metric_alert.critical, metric_alert.warning, metric_alert.resolved, metric_alert.open |
event_alert | event_alert.triggered |
Create a Sentry App
- Go to Settings > Developer Settings > New Internal Integration (for private use within your organization) or New Public Integration (to publish on the Sentry marketplace).
- Enter a name and webhook URL.
- Under Webhook, enable the resource categories you want to receive.
- Save the app and install it on your organization.
Sentry-Hook-Signature and uses the same HMAC-SHA256 scheme as Service Hooks.
Example issue.created payload
Respond to webhooks quickly
Sentry expects your endpoint to respond with a2xx status code within a few seconds. If your endpoint takes longer to process the payload, acknowledge the request immediately and handle the work asynchronously.
Retry behavior
Sentry retries failed webhook deliveries if your endpoint returns a non-2xx response or times out. Make your endpoint idempotent so that processing the same event twice does not cause unintended side effects. You can use the event id field to deduplicate.