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

# Webhooks

> Inbound provider webhooks and outbound automation webhook nodes.

## Inbound provider webhooks

These routes receive callbacks from external providers. They are not called by your integration.

### Stripe

Stripe webhook routes process platform and connected-account payment events:

```text theme={null}
POST /webhooks/stripe/platform
POST /webhooks/stripe/connect
```

These endpoints verify Stripe signatures, record webhook events, update checkout state, and trigger entitlement changes.

### Mailgun

Mailgun events update email delivery status:

```text theme={null}
POST /webhooks/mailgun/events
```

### AssemblyAI

AssemblyAI transcription callbacks update media transcription state:

```text theme={null}
POST /api/v1/media/webhooks/assemblyai
```

## Outbound webhook nodes (automations)

The automations engine ships a `webhook` node that POSTs a signed JSON payload to an endpoint you register. This is the current outbound webhook surface for customer integrations.

Webhook endpoints are hub-scoped and managed via:

```text theme={null}
POST   /api/v1/teams/{team_id}/hubs/{hub_id}/webhook-endpoints       create endpoint
GET    /api/v1/teams/{team_id}/hubs/{hub_id}/webhook-endpoints        list endpoints
DELETE /api/v1/teams/{team_id}/hubs/{hub_id}/webhook-endpoints/{id}   delete endpoint
```

Each endpoint has a signing secret (generated server-side if not supplied, encrypted at rest, never returned). Targets are validated against an SSRF guard — private, loopback, link-local, and cloud-metadata addresses are rejected. Delivery is asynchronous with exponential-backoff retries.

When the `webhook` node fires inside an automation it POSTs a payload containing the automation context and enrollment metadata to your registered URL. Use the signing secret to verify the `X-Mio-Signature` header on your receiver.

See the [Automations guide](/guides/automations) for the full node reference and lifecycle.

## Team-level outbound webhooks (Zapier-style)

General-purpose team-level outbound webhooks (trigger on any platform event, configurable outside of automations) are a planned feature tracked separately. For today's integrations, use the automation webhook node described above, API polling, or the checkout inspection endpoints.