Publer · Rate Limits

Publer Rate Limits

The Publer API documents a 429 Too Many Requests response code, indicating that per-account/per-workspace rate limiting is enforced, but specific numeric limits (requests per minute/hour) are not published in the public API reference. Asynchronous operations such as scheduling and publishing are accepted (202) and processed via a job queue, which decouples request submission from downstream social-network processing.

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

It captures 2 rate-limit definitions, measuring requests and jobs.

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

Tagged areas include Social Media, Scheduling, Publishing, Content Management, and Marketing.

2 Limits Throttle: 429
Social MediaSchedulingPublishingContent ManagementMarketingRate LimitingQuotasThrottling

Limits

Requests workspace
requests
see provider documentation
A 429 Too Many Requests response indicates throttling; numeric limits are not published.
Asynchronous Jobs workspace
jobs
queued
Schedule/publish operations return 202 Accepted with a job_id and are processed asynchronously via a job queue.

Policies

Async Processing
Scheduling and publishing are accepted (202) and processed asynchronously; poll GET /job_status/{job_id} for completion.
Backoff Strategy
Clients should implement retry with exponential backoff on 429 responses.
Downstream Network Limits
Each connected social network (Facebook, Instagram, X, LinkedIn, etc.) enforces its own publishing limits that apply on top of Publer's.

Sources