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 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.

For credit purchases, see the limits in Buy Credits.