---
title: "Rate limits"
description: "How many API requests you can make, and what happens when you exceed the limit."
---

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

# Rate limits

API requests are rate limited per team, per minute. If you need a higher limit, [contact support](/support/).

The limit is shared across the v2 and v3 API endpoints and the [MCP server](/mcp/), so requests from all of them count towards the same total.

## Exceeding the limit

Requests over the limit get `429 Too Many Requests`. Responses carry headers showing where you stand:

| Header | Meaning |
|---|---|
| `X-RateLimit-Limit` | Requests allowed per minute. |
| `X-RateLimit-Remaining` | Requests left in the current window. |
| `Retry-After` | On a `429`, seconds to wait before retrying. |

## Staying under the limit

- **Batch sends.** One [Send SMS](/api/sms/send/) request can carry up to 1000 messages, so you rarely need more than a few requests per minute to send.
- **Use webhooks instead of polling.** [Webhooks](/guides/webhooks/) deliver replies and delivery receipts as they happen, so you don't need to poll [List inbound messages](/api/inbounds/list/).
- **Back off on `429`.** Wait for `Retry-After` before retrying, rather than retrying straight away.

Source: https://dev.messageport.com.au/concepts/rate-limits/index.mdx