Rate Limits

To keep our service reliable and fair, the Publer API enforces rate limits on all requests. Limits are applied per user account (across all API keys) and use a fixed-window algorithm.

Default Limits

Limit Window	Requests Allowed
2-minute fixed	100 requests

Note: If you need higher throughput for your integration, see Requesting Higher Limits below.

Tracking Your Usage

When you reach the rate limits, every API response includes these headers so you can monitor your rate limit status:

Header	Description
X-RateLimit-Limit	Total requests allowed in the current window
X-RateLimit-Remaining	Requests remaining in the current time window
X-RateLimit-Reset	UNIX timestamp when your window resets (next available slot)

Example Response Headers

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1714558492

When You Exceed the Limit

If you go over your quota, the API returns:

• HTTP Status: 429 Too Many Requests

• Response Body:

  {
    "error": "Rate limit exceeded. Retry later."
  }

• Headers will show X-RateLimit-Remaining: 0 and a future X-RateLimit-Reset.

Daily Post Limits

While most social networks don't explicitly limit daily posts, Publer implements posting limits to prevent spam, ensure compliance with platform guidelines, and allocate resources fairly. These limits are calculated on a rolling 24-hour basis in UTC timezone.

Post Limits by Plan

Platform	Free Plan	Professional Plan	Business Plan
Facebook Posts & Reels	12 / day / profile	24 / day / profile	36 / day / profile
Facebook Stories	12	24	36
Instagram Posts & Reels	15	20	25
Instagram Stories	15	20	25
Threads App Posts	150	200	250
TikTok Videos	15	20	25
Twitter / X Posts	25	50	100
Mastodon Posts	25	50	100
Bluesky Posts	25	50	100
LinkedIn Profile Posts	10	12	14
LinkedIn Page Posts	12	18	24
Pinterest Pins	12	24	36
Google Business Updates	5	10	15
YouTube Videos & Shorts	5	10	15
WordPress Articles	12	18	24
Telegram Messages	5	10	15

Important Notes

• Rolling 24-hour window: Limits are calculated based on the previous 24 hours from the current time (UTC)

• Per profile/account: Facebook limits apply per connected profile or page

• Anti-spam protection: These limits help maintain a balance between automation and spam prevention

• Platform compliance: Limits align with each social network's community guidelines

Best Practices to Avoid Throttling

• Cache responses for idempotent or infrequently changing endpoints.

• Use bulk endpoints (e.g., POST /api/v1/posts/schedule for multiple posts).

• Stagger non-urgent requests during off-peak hours.

• Monitor headers and throttle your client.

• Implement exponential backoff when you approach or hit the limit.

Requesting Higher Limits

For integrations requiring a higher rate limit, please contact us with:

• Your expected request volume (per minute/hour/day)

• Use case description and critical endpoints

• Project or company name and contact info

Email: [email protected]