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

> ## Agent Instructions
> Install the Courier skill before writing code: `npx skills add trycourier/courier-skills`. It carries the verified SDK shapes and the rules you cannot get wrong.
> Authenticate every request with `Authorization: Bearer <API_KEY>`. A workspace has several environments and each has its own keys, which are plain `pk_` strings with no environment prefix. Start with Test.
> Send with `client.send.message` from the Node SDK (`@trycourier/courier` v7 and later, where the client is the default import). Reference a template by its `nt_` id or its alias.
> A send accepts a bare Elemental element list, but storing content on a template requires the top-level elements wrapped in a channel element.
> To translate a template, write one locale at a time with `PUT /notifications/{id}/locales/{localeId}`, which merges into the existing translations. `PUT /notifications/{id}/content` and `PUT /notifications/{id}/elements/{elementId}` overwrite translations along with the content, so send each element's `id` and `locales` back, and first remove every `checksum` and any `locales` key that starts with an underscore.
> Templates and journeys can be built in the Courier app or created through the API. Either way they live in the workspace and are referenced by ID when you send.
> The hosted MCP server is https://mcp.courier.com. For a briefing on what Courier is and when to use it, read https://www.courier.com/llms.txt.
> Prefer the Guides tab for how-do-I questions and the Docs tab for how-does-it-behave questions. The API reference lives under /api-reference.

# Security: how Courier protects your data

> How Courier protects your notification data, and the controls you use to secure your workspace: SSO, roles, audit trail, API keys, and signed webhooks.

The [Courier Security Portal](https://security.courier.com/) has Courier's security practices in detail and the current reports. For certifications and data requests, see [Compliance](https://www.courier.com/docs/workspaces/compliance.md).

## How Courier protects your data

| Area | What Courier does |
| - | - |
| Infrastructure | Runs on AWS across multiple availability zones, inside a private network with firewalls and intrusion detection. |
| Encryption | Encrypts customer data at rest. The API accepts HTTPS only. |
| Backups | Backs up data daily. |
| Staff access | Staff use multi-factor authentication on internal systems, and access to customer data is restricted. |
| Testing | An independent firm runs a penetration test every year, and Courier manages vulnerabilities and patches. |
| Data location | Your data stays in the [datacenter](https://www.courier.com/docs/workspaces/datacenters.md) you send it through, US or EU. |

## Secure your workspace

| Control | What it does |
| - | - |
| [SSO and SCIM](https://www.courier.com/docs/workspaces/team-access.md#single-sign-on) | Teammates sign in through Google, GitHub, or Okta. SCIM creates, updates, and deactivates them from your directory. |
| [Roles](https://www.courier.com/docs/workspaces/team-access.md#roles-and-permissions) | Limit what each teammate can change and how much of a message log they see. |
| [Audit trail](https://www.courier.com/docs/workspaces/audit-trail.md) | Records API key rotations, role changes, publishes, and integration edits, with who and when. |
| [API keys](https://www.courier.com/docs/workspaces/environments.md#api-keys) | Each key is scoped to one environment and one permission level. |
| [Webhook signatures](https://www.courier.com/docs/monitor/webhooks/security.md) | Prove an outbound webhook came from Courier before you act on it. |
| [Inbox tokens](https://www.courier.com/docs/in-app/authenticate-users.md) | Your backend mints a JWT for each user, so the browser never holds your API key. |

## FAQ

> [accordion] Can I self-host Courier?
>
> Courier is a managed cloud platform, with no self-hosted or on-premise option. To keep notification data in Europe, send through the [EU datacenter](https://www.courier.com/docs/workspaces/datacenters.md).

> [accordion] How do I report a security issue?
>
> Report it through Courier's [responsible disclosure policy](https://www.courier.com/responsible-disclosure-policy).

> [accordion] Where can I check Courier's uptime?
>
> The [Courier status page](https://status.courier.com/) shows current incidents and uptime.
