Social Media API Rate Limits: A Platform-by-Platform Reference
Every platform sets its own rate limits, and they don't agree on units, reset windows, or what counts against the cap. This is the current reference as of September 2026, gathered from each platform's own documentation. Limits change without notice on every one of these platforms — verify against the platform's current docs before you build a hard dependency on a specific number.
#The Reference Table
| Platform | Write limit | Reset window | Notes |
|---|---|---|---|
| X (Twitter) | 100 posts per user | 15 minutes | Also capped at 10,000 posts per app per 24 hours; three separate ceilings can apply at once (endpoint, app, account). |
| LinkedIn (Share on LinkedIn) | ~150 API calls per member | 24 hours (UTC) | Personal profile only (w_member_social). Some endpoints cap as low as 10 requests/day per member. Limits aren't published — visible only in the Developer Portal after your first call. |
| LinkedIn (Community Management API) | 100,000 calls per app | 24 hours | Company Pages (w_organization_social), requires review + registered legal entity. |
| Facebook Pages | 4,800 × engaged users | 24 hours | Formula-based, not a fixed number — scales with how many people interact with the Page. Exponential backoff is the standard mitigation on 429s. |
| Instagram (Graph API) | 25 media publishes | Rolling 24 hours | Meta's own docs are inconsistent between 25, 50, and 100 depending on which page you read — 25 is the number developers hit in practice. Query /content_publishing_limit for your account's real usage. |
| TikTok (Content Posting API) | 6 requests/minute per user token; ~15–25 videos/day per account | Rolling 1 minute (per-minute cap); 24 hours (daily cap) | The daily cap is shared across every app posting to that account, including manual posts from the TikTok app itself. |
| YouTube (Data API v3) | 100 upload calls/day (own bucket since June 2026); 10,000 units/day for everything else | 24 hours | Uploads used to cost ~1,600 units each against the shared pool; they're now billed separately at 1 unit each with their own 100/day cap. |
| 100 requests/second (Standard access) | Per second | Trial access is capped at 1,000 requests/day total. Category-specific limits apply on top (e.g., ads_write at 400/minute). |
#Why These Numbers Don't Map Cleanly Onto Each Other
Notice that no two platforms measure the same thing. X and Pinterest count raw API requests. Instagram and TikTok count published media items. Facebook's limit isn't a number at all — it's a formula tied to how engaged your audience is. LinkedIn's limits are undocumented until you've already made a call.
This is the actual argument for not writing rate-limit handling per platform yourself: there's no shared abstraction to build once. A backoff strategy tuned for X's fixed 15-minute window does nothing useful against Facebook's engaged-user formula, and neither helps with TikTok's shared-across-all-clients daily cap. Each platform needs its own logic, tracked per connected account, refreshed as the platform's own limits change — which they do without notice, as several of the sources above note explicitly.
#How a Posting Queue Absorbs This Instead
A posting API with a real queue sits between your code (or your agent) and each platform's actual limit. You send a post; if there's room under that platform's current cap, it goes out immediately. If not, it queues and sends as soon as the window clears, without you writing retry logic, tracking reset timestamps, or parsing x-rate-limit-reset headers yourself.
This matters more, not less, once an AI agent is the thing calling the API. A human posting a few times a day rarely brushes against any of these caps. An agent running a content batch, backfilling a queue, or retrying on ambiguous errors can hit X's 100-per-15-minutes limit or Instagram's 25-per-day limit within a single session — see Best Social Media API for AI Agents in 2026 for what else changes at agent scale, and Social Media API for AI Automation for the broader automation picture.
If you're deciding whether to build this queue yourself or use a provider that already has it, Build vs Buy: The True Cost of a Social Media API Integration walks through the actual cost tradeoff — maintaining seven platforms' worth of drifting rate-limit logic is real, ongoing engineering time, not a one-time build.
Schedule & Chill queues posts against each platform's real, current limits so you don't hand-roll this — it's free right now, no credit card, no trial timer, with up to 2 connected accounts and 500 posts a month. If you're comparing this against other unified APIs on price and features rather than building it yourself, see Ayrshare Alternatives for Developers or Buffer API Pricing in 2026.
For the broader concept this reference sits under, see What Is a Unified Social Media API?.
#Frequently Asked Questions
Which platform has the tightest rate limit for automated posting? TikTok, in practice — its ~15–25 videos/day cap is shared across every app and the manual TikTok app itself, so an automated tool isn't getting its own separate allowance the way it might on X or Pinterest.
Do rate limits apply per app or per connected account? Both, usually as separate ceilings. X and YouTube cap per-app usage and per-account usage separately; hitting either one blocks further requests even if the other has headroom.
What happens if my app exceeds a platform's rate limit? The platform returns an error, commonly HTTP 429, and the request fails. Some platforms (Facebook, X) return a reset time in the response headers; others, like LinkedIn, don't document the limit at all until you've already hit it.