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

# Limits

> Rate limits and size limits of the API.

| Limit | Value |
| - | - |
| Requests | 10 per second per API key |
| Recipients per email | 50 across `to`, `cc` and `bcc` |
| Tags per email | 10, each up to 256 characters |
| Custom headers per email | 20 |
| Subject | 998 characters |
| Active API keys | 20 per team |
| Sending domains | 10 per team |
| Idempotency keys | Kept 24 hours |

## Rate limiting

Going over 10 requests per second returns `429` with the code `rate_limited`. The response carries `Retry-After` with the number of seconds to wait. Back off and retry; with an [idempotency key](/guides/idempotency), retries are safe.

## Sending reputation

PulseSend watches each team's bounce and complaint rates, the numbers mailbox providers judge senders by. Keep bounces under 4% and complaints under 0.08%.

Rates are computed on live emails from the last 30 days whose outcome is known (delivered, bounced or marked as spam), once you have at least 100 of them. Test emails never count. They are checked every time a bounce or complaint comes in.

When a rate goes over its limit, sending is paused for the whole team: every send returns `403` `team_paused`, the team owner gets an email and the dashboard shows a banner. Clean up your recipient list, then contact support to reactivate sending. Rates start again from zero after reactivation.

Keep both rates low by sending only to people who asked for your emails and removing addresses that bounce.


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