> For the complete documentation index, see [llms.txt](https://help.blotato.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.blotato.com/api-and-mcp-concepts/rate-limits.md).

# Rate limits

Identify request-rate limits and retry behavior separately from plan allowances, credits, and platform restrictions.

Blotato applies route-specific request limits. These limits are separate from subscription limits, credits, and social platform publishing limits.

| Operation                                                               | Requests per minute |
| ----------------------------------------------------------------------- | ------------------: |
| Create post                                                             |                  30 |
| List posts or get post submission status                                |   60 for each route |
| Get post analytics                                                      |                  60 |
| Upload media from a URL with `POST /v2/media`                           |                  30 |
| Create a presigned upload URL                                           |                 120 |
| List Pinterest boards                                                   |                  45 |
| List comments or get a comment                                          |   60 for each route |
| Post a comment                                                          |                  30 |
| List conversations, get a conversation, list messages, or get a message |   60 for each route |
| Send a message                                                          |                  30 |
| List or get DM automations, runs, logs, or analytics                    |   60 for each route |
| Create, update, delete an automation, or update a trigger               |   30 for each route |

This table covers the listed routes. Consult each endpoint's reference for other limits. MCP tools call the underlying REST routes, so status polling and tool sequences consume requests too.

## Handle a limit response

1. Stop requests to the limited route after `429`.
2. Wait for the retry interval when the response supplies one.
3. Reduce concurrency and request frequency before resuming.
4. Use [polling intervals](/api-and-mcp-concepts/async-jobs-and-polling.md) rather than repeated status calls without a delay.

A platform publishing restriction is a different limit. For example, the Starter plan's TikTok restriction counts 3 distinct TikTok accounts posted to during a rolling 24-hour window. It is not an API request-per-minute limit or a count of connected accounts. See [TikTok limitations](/social-accounts-and-platform-faqs/tiktok/limitations.md).

For credit purchases, see the limits in [Buy Credits](/rest-api-reference/credits.md#buy-credits).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.blotato.com/api-and-mcp-concepts/rate-limits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.