Postiz · Rate Limits

Postiz Rate Limits

The Postiz Public API applies an hourly request rate limit per API key. Postiz documents a default limit on the order of ~30 requests per hour; this counts API requests, not published posts, so a single request can schedule many posts. On self-hosted deployments the limit is configurable. Separately, Postiz Cloud plans impose monthly post-volume and channel quotas (see plans), which are commercial quotas rather than per-second API throttles.

Postiz Rate Limits is the machine-readable rate-limit profile for Postiz on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, posts, and channels.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Social Media, Scheduling, Open Source, Content, and Marketing.

3 Limits Throttle: 429
Social MediaSchedulingOpen SourceContentMarketingRate LimitingQuotasThrottling

Limits

Requests Per Hour api_key
requests
see provider documentation (~30/hour default)
Counts API requests, not posts; configurable on self-hosted instances.
Monthly Posts (Cloud quota) account
posts
per plan (e.g. 400/month on Standard, unlimited on Team and above)
Commercial plan quota, not a per-second API throttle.
Channels (Cloud quota) account
channels
per plan (5 / 10 / 30 / 100)
Number of connectable integrations; unlimited concept does not apply on self-hosted.

Policies

Configurable Self-Hosted Limits
Self-hosted operators can adjust the API rate limit for their own instance.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses.
Idempotent Deletes
A 404 on a delete means the post is already gone and is safe to ignore.

Sources