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

# Team limits

> Default Sendmux team limits, when increase requests appear, and what happens at the hard limit.

Sendmux sets team-level limits for resources that can grow quickly. You can request more capacity from the relevant page when usage reaches the request threshold.

## Default limits

Each new team starts with these limits:

| Resource         | Default limit | Guide                                        |
| ---------------- | ------------- | -------------------------------------------- |
| Domains          | 25            | [Domains](/docs/guides/domain-management)         |
| Mailboxes        | 50            | [Mailboxes](/docs/guides/mailboxes)               |
| Sending accounts | 200           | [Sending accounts](/docs/guides/sending-accounts) |
| Webhooks         | 10            | [Webhooks setup](/docs/guides/webhooks-setup)     |
| Credentials      | 100           | [API keys](/docs/guides/api-keys)                 |

<Note>
  Credentials include manual API keys across all key types and connected apps.
  Pending mailbox credential creation can also reserve capacity until it
  finishes. The **API Keys** page shows both credential classes in that total.
</Note>

## Request an increase

When a resource reaches **80%** of its current limit, Sendmux shows **Request increase** near the usage text on that page. API clients can request more sending-account capacity with `POST /providers/limits/sending-accounts/request-increase`. Submit the request once. The page then shows the pending request state.

You can have one pending request per team and resource. Sendmux emails the requester when the request is approved or denied. Approved increases apply immediately.

## At the hard limit

When usage reaches the full limit, creation is blocked for that resource until the limit is raised or you delete an existing item.

API create requests return `409 limit_exceeded` when the limit has been reached. This error is not retryable. Request an increase or reduce usage before trying again.

## Email volume

Sendmux does not add a separate cap to incoming or outgoing email volume through this team-limit system.

Sending through the managed Amazon SES account still follows its daily sending limit. Request a review from **Accounts** or with `POST /providers/shared-amazon-ses-limit-request`. Your own providers may also enforce provider-side sending limits.

## Related guides

<Columns cols={2}>
  <Card title="Domains" icon="globe" href="/docs/guides/domain-management">
    Add and verify custom domains.
  </Card>

  <Card title="Sending accounts" icon="send" href="/docs/guides/sending-accounts">
    Add providers and request managed account limit increases.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/docs/guides/webhooks-setup">
    Subscribe to delivery and mailbox events.
  </Card>

  <Card title="API keys" icon="key" href="/docs/guides/api-keys">
    Create, rotate, and revoke scoped keys.
  </Card>

  <Card title="API errors" icon="triangle-alert" href="/docs/api/errors">
    Handle `limit_exceeded` responses in API clients.
  </Card>
</Columns>