Plan and request limits
Distinguish plan defaults, account-specific contact limits, upload constraints, and API request rate limits.
Compact reference for agents making REST requests. All endpoint paths below are relative to https://backend.blotato.com/v2. For task instructions, read the workflow guide. For tool calls, use the MCP reference.
Plan limits
Blotato has 3 plans (starter, creator, agency). Plan defaults:
starter creator agency
Max connected social accounts 20 40 100
Max media upload size 400 MB 1 GB 1 GB
Queued scheduled posts 200 1000 3000
Scheduling horizon (months) 9 9 9
Active contacts per month 1,000 6,000 15,000
Analytics metric fields 25 all all
Analytics checkpoints/post 4 18 20
Analytics collection window 30 days 30 days 90 days
Active contacts are unique per connected social account. The same person reached through 2 connected Facebook Pages counts as 2 active contacts. Reaching the same person again through the same connected account during the monthly window does not add another contact.
GET /users/me/usage returns accounts, contacts, and contactsLimit. contactsLimit is an integer or "unlimited". Use contactsLimit as the user's current monthly active-contact limit, not the connected-account cap. Some accounts have a custom monthly active-contact limit.
The scheduling horizon is 9 months on EVERY plan. It does not scale with the plan.
A DM sent by a DM automation counts toward active contacts like any other send.
Facebook Pages and LinkedIn Company Pages count toward the cap.
* Facebook: The personal Facebook login is the required OAuth parent for its Pages. It must remain connected while those Pages are connected. Disconnecting the login removes every Page authorized through it. The login does not count toward the cap. Each connected Page counts as one account.
* LinkedIn: Each profile and each connected company Page each count as one account.
Plan validation might reject submission before background work starts. A successful
create response is not proof of completion. Follow the operation-specific status
endpoint and report its error when processing fails.Rate limits
Plan upload limits do not replace the target platform's file restrictions. A rate-limit response does not establish whether an earlier write succeeded. Follow rate-limit recovery and look up existing submission IDs before repeating a create request. See billing and credits for plan details.
Return to the agent reference index.
Last updated