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

# Overview

> Connect the services subscriber.dev sends through and listens to.

Integrations connect an environment to your other services. There are two kinds:

* **Email providers** send your emails. Each environment needs at least one.
* **Event sources** start and stop workflows when something happens, such as a Stripe trial starting.

> [card] [Resend](https://docs.subscriber.dev/integrations/resend.md)
>
> Resend's email API, with bounces and spam complaints handled.

> [card] [Postmark](https://docs.subscriber.dev/integrations/postmark.md)
>
> Postmark's email API, with bounces and spam complaints handled.

> [card] [Amazon SES](https://docs.subscriber.dev/integrations/ses.md)
>
> Amazon's email service, with bounces and spam complaints handled.

> [card] [SMTP](https://docs.subscriber.dev/integrations/smtp.md)
>
> Send through any SMTP provider.

> [card] [Cloudflare Email](https://docs.subscriber.dev/integrations/cloudflare.md)
>
> Cloudflare's email sending API, with automatic bounce handling.

> [card] [Stripe](https://docs.subscriber.dev/integrations/stripe.md)
>
> Start workflows from trials, subscriptions and failed payments.

## Manage integrations

Or ask [your agent](https://docs.subscriber.dev/mcp.md): "Which integrations are connected to production?"

> [tab] CLI
>
> ```bash theme={null}
> subscriber integrations list
> subscriber integrations get smtp
> subscriber integrations remove smtp
> ```

> [tab] TUI
>
> Open **Integrations**. Press `n` to connect one, or choose one to change or remove it.

> [tab] API
>
> ```bash theme={null}
> curl https://api.subscriber.dev/integrations -H "x-api-key: $KEY"
> ```
>
> Connect or update one with `PATCH .../integrations/<type>`, and remove it with `DELETE`.

Each environment has its own integrations, so staging can send through a test provider while production uses your real one.

Settings are checked before they're saved, so a wrong password fails straight away. Passwords, tokens and keys are encrypted and never shown again. To change a setting, send all the settings again; leave out the secret to keep the saved one.

## More than one email provider

If sending through one provider fails, subscriber.dev tries the next, so an outage doesn't stop your emails. The first one you connect is tried first. To change the order:

```bash theme={null}
subscriber integrations set-primary cloudflare
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.