If you schedule posts, pull engagement data, or auto-share new articles to Twitter, LinkedIn, Facebook, or Instagram, you’re using an API behind the scenes—whether you know it or not. Every social media platform sets rate limits: hard ceilings on how many requests your account (or the app acting on your behalf) can make in a rolling window. Hit that limit and your scheduler stops posting, your analytics dashboard goes blank, or your cross-posting workflow silently fails.
Most solo operators don’t think about API limits until they trip one. This guide explains where the walls are, what happens when you hit them, and how to design your workflow so you don’t.
What counts as an API call
Every interaction between an app and a social platform is an API request. Publishing a post is one call. Reading your follower count is another. Fetching the last 50 posts from your timeline might be one or fifty, depending on how the endpoint works. If you use a scheduling tool like Publer, Buffer, or Hootsuite, each action the tool takes on your behalf—posting, editing, deleting, reading replies—burns a request from your quota.
The quota resets on a schedule: per minute, per hour, per day, or per app. Some platforms count per user; others count per application. If you connect three tools to the same Twitter account, all three may share the same pool of allowed requests.
Where the major platforms set the ceiling
Twitter’s (X’s) API tiers changed significantly in early 2023 and again in 2024; as of November 2026, the free tier no longer exists for third-party apps, and the Basic tier (around $100/month, checked November 2026) allows 10,000 posts per month and 1,000 read requests per month. If you schedule more than ~300 posts per month or pull analytics daily, you’ll exceed the read cap. The Pro tier raises both limits but costs several hundred dollars monthly.
LinkedIn’s API documentation (checked November 2026) imposes different limits by endpoint. User-generated content (posts) is capped at 150 write requests per person per day for organic shares, and 25 per day for certain image or video operations. If you post once an hour around the clock, you’re under the wire—but if your scheduler retries failed uploads or you’re using multiple tools, you can hit the wall.
Meta platforms (Facebook and Instagram) use a two-tier system: per-user and per-app. Facebook’s Graph API (checked November 2026) applies a rate limit of 200 calls per user per hour for most endpoints, but also enforces an app-level budget that scales with your app’s usage tier. Instagram’s API shares similar constraints. If you run a scheduling tool that serves multiple clients from one app ID, the app-level limit matters more than your personal ceiling.
TikTok and Pinterest also enforce API quotas, but most solo operators use web-based schedulers rather than direct API access, so these limits typically affect the tool vendor, not you—until the vendor’s quota runs out and posts stop going through.
What happens when you hit the limit
Most platforms return an HTTP 429 status code (“Too Many Requests”) and a header indicating when the quota resets. Well-designed tools queue your request and retry after the window rolls over. Poorly designed tools log an error, show a generic failure message, or silently drop the task. You won’t know your post didn’t publish unless you check manually.
Some platforms temporarily block your app or account if you exceed limits repeatedly. Twitter has historically suspended API access for 15 minutes to several hours after sustained violations. LinkedIn and Meta may throttle your requests progressively: your first dozen succeed, then every other one fails, then only one in ten goes through.
How to stay under the ceiling
Batch your API calls instead of making real-time requests every few minutes. If you pull analytics, fetch data once per day and cache it locally rather than querying on every page load. If you cross-post from RSS, deduplicate before sending so you don’t publish the same article twice and burn two quota slots.
Use tools that respect rate limits and surface quota information. Publer, for example, queues posts and spaces them out to avoid bursts. Buffer provides visibility into when posts are scheduled and warns you if you’re approaching platform limits. If you’re building custom workflows with Zapier or Make, add delays between steps and check the task history for 429 errors.
If you routinely hit limits, consider whether you need real-time data or can work with a delay. Most solo operators don’t need follower counts updated every hour. A nightly sync is enough. That single shift can cut your monthly API usage by 90 percent.
Finally, if you manage multiple brands or clients, isolate each account’s automation. Don’t chain five Instagram profiles to the same Zapier app; Meta’s app-level limit will choke all five when any one gets busy. Use separate API keys or separate tool accounts where possible.
When to pay for higher limits
If your workflow depends on frequent publishing—hourly social posts, real-time comment monitoring, or live dashboard updates—and you’re brushing the free-tier ceiling every week, upgrading to a paid API tier or a higher scheduler plan is cheaper than the opportunity cost of silent failures. Twitter’s Basic tier may feel expensive at $100/month, but if a missed post costs you affiliate clicks or sponsorship deliverables, the insurance is worth it.
Check your tool’s API usage dashboard (if it has one) or request logs every month. If you’re consistently under 50 percent of any limit, you have headroom. If you’re above 80 percent, you’re one workflow change away from breaking.
Want more infrastructure deep-dives like this? Subscribe to One Two Three Send and we’ll send you one operator-to-operator breakdown every morning.
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.