If you publish to multiple social platforms through a scheduler or automation tool, you’ve already used an API—whether you know it or not. Every time your tool posts on your behalf, it makes a call to that platform’s application programming interface. And every platform caps how many calls you can make in a given window.
Hit that cap, and things stop working. Not always with a clear error message. Sometimes your posts just don’t go out. Sometimes they queue silently. Sometimes your entire account gets temporarily locked.
Here’s what actually happens when you hit rate limits, how platforms differ, and what your scheduling tool does—or doesn’t do—to protect you.
How platforms meter API calls
Rate limits aren’t uniform. Twitter’s API (now X) uses a 15-minute rolling window for most endpoints. Instagram’s Graph API counts requests per hour and per day. LinkedIn measures calls per application and per user token. Facebook uses a complex credit system that resets hourly but penalizes burst traffic.
Most solo operators don’t interact with these APIs directly—they use tools like Publer, Buffer, or Hootsuite. But those tools share API quota across all their users. When you schedule a post, your tool makes the call on your behalf using either a shared app token or an individual user token tied to your OAuth login.
Shared tokens mean one power user can exhaust the quota for everyone. Individual tokens mean your usage is isolated, but you’re responsible for staying under the threshold—and most tools don’t surface how close you are.
What breaks when you hit the limit
The immediate symptom: your scheduled post doesn’t publish. What happens next depends on the platform and the tool.
Twitter rate limits return a 429 Too Many Requests response. Most schedulers retry automatically after the window resets. But if you’ve queued 50 posts to go out in a 15-minute span, only the first batch publishes. The rest either fail silently or get pushed to the next available slot—sometimes hours later, sometimes never.
Instagram’s API doesn’t just reject the call. Repeated limit violations can trigger a temporary block on your account, not just the tool. That block can last 24 hours. During that window, even manual posts from the Instagram app may be throttled or flagged as spam.
LinkedIn’s API returns a Retry-After header telling your tool how long to wait. Well-designed schedulers respect that. Poorly designed ones hammer the endpoint every few seconds, which extends the lockout and can flag your app token as abusive.
Facebook’s credit system is the most opaque. You don’t get a hard cutoff—you get throttled. Posts slow down. Media uploads time out. The tool may report success while the post sits in limbo for 20 minutes before finally appearing.
How schedulers handle rate limits (or don’t)
Not all tools handle this gracefully. Some retry intelligently. Some fail and log the error. Some do nothing and leave you wondering why yesterday’s post never went live.
Publer, for instance, uses individual OAuth tokens and queues retries when it hits a rate limit. If a post fails due to API throttling, it shows a warning in your dashboard and attempts redelivery during the next window. You can manually re-queue if needed.
Buffer retries up to three times, spaced 60 seconds apart. After that, the post is marked as failed, and you get an email. No automatic rescheduling—you have to manually repost or edit the queue.
Hootsuite logs the failure but doesn’t always surface it prominently. If you don’t check the message center, you might not know a post didn’t go out until a follower asks why you went silent.
Zapier and Make (formerly Integrabuild) treat social posts as individual automation tasks. If an API call fails, the entire automation fails. Depending on your plan, it may retry once or stop completely. There’s no built-in queue—just a failed task log you have to monitor.
How to avoid hitting the wall
First, batch your posts sensibly. Don’t schedule 20 LinkedIn updates to publish in the same hour. Spread them across the day. Most platforms are fine with one post every 15–30 minutes; anything tighter risks hitting burst limits even if your daily quota is fine.
Second, know your tool’s architecture. Does it use shared or individual tokens? If shared, you’re at the mercy of other users’ activity. If individual, you control your own quota—but you’re also solely responsible for staying under it.
Third, monitor your dashboard. Most schedulers show failed posts, but not all surface why they failed. Look for terms like “rate limit,” “throttled,” or “429 error.” If you see repeated failures at the same time of day, you’re likely hitting a window boundary.
Fourth, use native scheduling when possible for high-volume accounts. Facebook’s Creator Studio, LinkedIn’s native scheduler, and Twitter’s own scheduling UI don’t count against third-party API limits. If you’re publishing more than 10 times a day to a single platform, native tools are often more reliable—and free.
When rate limits actually help
Rate limits aren’t purely punitive. They prevent spam, protect platform performance, and force you to think about whether you’re over-posting. If you’re routinely hitting API caps, the bottleneck isn’t the platform—it’s your publishing cadence.
One operator I spoke with was scheduling 15 Twitter threads a day through Zapier, triggered by new blog posts in an RSS feed. Half the threads never posted. The issue wasn’t Zapier—it was that 15 threads in 24 hours, each requiring multiple API calls to thread replies together, exceeded Twitter’s per-user limit. Switching to three threads a day, manually curated, worked better and got more engagement.
Rate limits force editorial discipline. If you can’t automate your way to volume, you have to prioritize quality.
One Two Three Send is written for operators who want their tools to work predictably. If you run into a rate-limit mystery—or solve one—reply and let us know. We’ll cover it.
Heads up — some links in this article are affiliate links. If you sign up through them, we may earn a small commission at no extra cost to you. We only recommend tools we use ourselves.