Skip to main content
The Postzee API enforces rate limits to ensure fair usage and platform stability. Limits vary by endpoint type.

​
Rate limits by endpoint

Endpoints with explicit per-minute limits override the global default. Most read endpoints (channels, credits, posts, jobs) fall under the global 30/hour limit. AI generation endpoints have their own higher-frequency limits.

​
MCP server rate limits

​
Rate limit headers

When you approach or exceed a rate limit, the API returns standard rate limit headers:

​
Exceeding the limit

When you exceed the rate limit, the API returns:
What to do: Wait for the rate limit window to reset (check the X-RateLimit-Reset header), then retry your request.

​
Best practices

  • Space out AI generation requests — limit to 10 per minute for image/video generation
  • Cache model lists — the available models don’t change frequently, so cache responses from /image-models and /video-models
  • Poll job status reasonably — check every 5-10 seconds, not every second
  • Use batch operations — when generating multiple images, use generate-media with quantity: 2-4 instead of multiple generate-image calls
  • Handle 429 gracefully — implement exponential backoff when rate limited

​
Limits by plan

Rate limits are the same across all paid plans. The API is not available on the Free plan.