Limits & quotas

The API itself works on every plan. What varies is how much you can do — enforced per request against the workspace’s plan.

Plan quotas

Plan tier governs:

• Monthly posts — how many posts the workspace can publish per calendar month.
• Storage — total hosted media.
• Connected accounts — how many platforms can be linked.
• AI credits — see AI credits.

When a quota is hit, the request fails with a specific error code (for example post_limit_reached, returned with HTTP 409). Branch on the code:

{ "code": "post_limit_reached", "message": "The monthly post limit for this plan has been reached." }

Note

There is no per-call rate limit on the public API today — requests are gated by the plan quotas above, not by requests-per-second. Build retries with sensible backoff anyway, and don’t hammer the API in tight loops.

Per-platform content rules

Each platform enforces its own content and media limits. Always read them from GET /public/v1/platforms/{id}/schema rather than hard-coding, since some values (like the available TikTok privacy_level options) are account-specific.

TikTok — the platform offered today — enforces:

• Content up to ~2,200 characters.
• Media: exactly one video, or a 1–35 image photo carousel. You cannot mix images and videos in one post.

Device-flow polling

The CLI device flow has its own pacing rules from RFC 8628:

• Poll /auth/device/token no faster than the returned interval (5 seconds).
• If you poll too fast you get { "error": "slow_down" } — add 5 seconds to your interval and continue.
• Codes expire after 10 minutes ({ "error": "expired_token" }).