> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/crm-marketing/push-message-guide/send/rate-limit.md).

# Rate Limit

During a push campaign, you can distribute message sending to prevent service traffic overload.

By default, messages are sent at up to 100,000 per minute considering APNS/FCM throughput, and you can set a more conservative limit if desired.

* Rate Limit
  * You can set the maximum number of messages to be sent at once per minute to prevent service traffic overload.
  * Note that setting the number of messages per minute too low may delay message delivery.
  * For event-based and API-based sends, since large volumes are not sent at once, the rate limit feature is not provided. The rate limit feature is only available for schedule-based sends.

![Schedule-based > Rate Limit](/files/yevlZJBHMU1XHXIQyGTb)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackle.io/en/crm-marketing/push-message-guide/send/rate-limit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.