---
title: "Social media API rate limits 2026: every network in one table"
description: "Posting caps, call limits and project quotas for Instagram, Facebook, Threads, TikTok, YouTube, X, LinkedIn, Pinterest and Google, from each network's docs."
url: https://rizamo.com/guides/social-media-api-rate-limits/
---

# Social media API rate limits 2026: every network in one table

Every social network limits what an app can do through its API, but "rate limit" means three different things depending on the network: how many posts one account can publish in a day, how many calls your app can make in a window, and how much quota your whole project gets. Mixing them up is how a scheduler ends up retrying a post that can only go out tomorrow.

This page puts the limits that matter for publishing in one table, each linked to the network's own docs as they read in November 2026, then says how to read each one at runtime and what to do when you hit it.

## The short version

- **Posts per account** are the limit you will hit first: 100 a day on Instagram, 250 on Threads, around 15 on TikTok, 30 Reels on a Facebook Page.
- **Calls per window** rarely stop a publisher. Meta scales them with each account's audience; X, Pinterest and TikTok set them per endpoint and per minute.
- **Project quotas** are shared by every account your app serves: YouTube's 100 uploads a day, LinkedIn's daily app limit, Pinterest's Trial tier.
- **Some caps are shared with other apps.** TikTok's daily post cap counts every app that posts for the creator, so your own count is not enough ([content sharing guidelines](https://developers.tiktok.com/doc/content-sharing-guidelines)).
- **Read the limit, do not hardcode it.** Instagram and Threads have an endpoint for it; X, Pinterest and Meta send headers. Meta's own pages disagree on Instagram's number.

## Three kinds of limit

| Kind | What it counts | Who shares it | What to do when you hit it |
| --- | --- | --- | --- |
| Posts per account | Published posts in a moving 24 hours | One account, sometimes across apps | Hold the post until there is room. Retrying does not help |
| Calls per window | Requests per minute, hour or day | One token, one account or your app | Back off and try again in minutes |
| Project quota | Units or calls per day for the whole app | Every account your app serves | Stop until the reset, or ask the network for more |

## Every network in one table

| Network | Posts per account | Calls | Project or app quota | Read it at runtime |
| --- | --- | --- | --- | --- |
| Instagram | 100 in 24 h (50 on another of Meta's pages). Carousel counts as one. 400 containers in 24 h | 4800 x the account's impressions, per 24 h | None documented for publishing | `content_publishing_limit` endpoint, `X-Business-Use-Case-Usage` header |
| Facebook Pages | 30 Reels in 24 h. No daily count for feed posts in the docs we read | 4800 x the Page's engaged users, per 24 h (Page token) | 200 x users per hour (user or app token) | `X-Business-Use-Case-Usage` and `X-App-Usage` headers |
| Threads | 250 posts, 1,000 replies and 100 deletions in 24 h. Carousel counts as one | 4800 x impressions, at least 10, per 24 h | None documented | `threads_publishing_limit` endpoint |
| TikTok | About 15 direct posts a day, shared with every app. 5 pending inbox drafts in 24 h | 6 init calls a minute per token, 30 status calls a minute | Creators per day, set at your audit (5 before it) | None for the daily cap: the `spam_risk_too_many_posts` error |
| YouTube | No count per channel; `uploadLimitExceeded` when a channel uploads too much | Units: a read costs 1, a write 50 | 100 uploads and 10,000 units a day per Google Cloud project, reset at midnight Pacific | Quotas page in the Google Cloud console |
| X | 100 posts per user in 15 min | Per endpoint, per 15 min and per 24 h | 10,000 posts per app in 24 h. Usage is billed apart from rate limits | `x-rate-limit-*` headers |
| LinkedIn | Not published | Daily, per member and per app, reset at midnight UTC | Not published | Analytics tab in the Developer Portal |
| Pinterest | Not published | Standard: 100 writes a minute per user per app | Trial: 300 writes and 1,000 calls a day per app | `x-ratelimit-*` headers |
| Google Business Profile | None for local posts on the limits page | 300 requests a minute | Per Google Cloud project | Quotas page in the Google Cloud console |

The sections below give the source for each row.

## Instagram

- Each account can publish 100 posts through the API in a moving 24 hours, enforced on `media_publish`; a carousel counts as one ([content publishing](https://developers.facebook.com/documentation/instagram-platform/content-publishing)). The same page says 50 in its carousel section, so read the number from `content_publishing_limit` ([reference](https://developers.facebook.com/documentation/instagram-platform/instagram-graph-api/reference/ig-user/content_publishing_limit)). The account in our [Instagram API guide](/guides/how-to-post-to-instagram-via-api/) returned 100 in October 2026, and its count lagged a post behind.
- An account can create at most 400 containers in a rolling 24 hours ([IG User Media](https://developers.facebook.com/documentation/instagram-platform/instagram-graph-api/reference/ig-user/media#limitations)). A publisher that creates a container and gives up on it still spends one.
- Calls count against "4800 * Number of Impressions" in a rolling 24 hours, where impressions are how often the account's content reached a screen in that time ([rate limiting](https://developers.facebook.com/docs/graph-api/overview/rate-limiting)). A small or new account has a smaller budget for reads.

## Facebook Pages

- A Page can publish 30 Reels through the API in a moving 24 hours ([Reels publishing](https://developers.facebook.com/documentation/video-api/guides/reels-publishing)). Meta recommends that your app enforce the limit too, especially when it schedules posts (same page).
- We found no daily count for feed posts in Meta's Pages docs. Numbers you see elsewhere, such as 25 a day, do not come from Meta's pages, so treat a throttling error as the real limit.
- Calls with a Page token count against "4800 * Number of Engaged Users" in 24 hours. Calls with a user or app token fall under the app's limit, "200 * Number of Users" an hour ([rate limiting](https://developers.facebook.com/docs/graph-api/overview/rate-limiting)).

## Threads

Threads has its own page of limits, and one endpoint reports all of them ([overview](https://developers.facebook.com/documentation/threads/overview)):

- 250 posts in a moving 24 hours, enforced on `threads_publish`. A carousel counts as one.
- 1,000 replies and 100 deletions in a moving 24 hours.
- Calls: "4800 * Number of Impressions" in 24 hours, with impressions counted as at least 10, so a new profile still gets 48,000 calls.

## TikTok

- Direct Post allows "typically around 15" posts a day per creator, and the cap counts every app that posts for that creator ([content sharing guidelines](https://developers.tiktok.com/doc/content-sharing-guidelines)). TikTok gives no endpoint to read it: you find out from `spam_risk_too_many_posts` ([direct post](https://developers.tiktok.com/doc/content-posting-api-reference-direct-post)).
- Before your app passes TikTok's audit, at most 5 creators can post through it in 24 hours; after it, the cap comes from the usage you declared in the audit form ([content sharing guidelines](https://developers.tiktok.com/doc/content-sharing-guidelines)).
- Each token can make 6 init calls a minute ([direct post](https://developers.tiktok.com/doc/content-posting-api-reference-direct-post)) and 30 status calls a minute ([get post status](https://developers.tiktok.com/doc/content-posting-api-reference-get-video-status)). An inbox draft counts toward a limit of 5 pending in 24 hours ([upload](https://developers.tiktok.com/doc/content-posting-api-reference-upload-video)).

The details, with the audit and the posting screen: [TikTok Content Posting API guide](/guides/tiktok-content-posting-api/).

## YouTube

- A Google Cloud project gets 100 `videos.insert` calls a day in its own bucket, plus 10,000 units a day for every other call. A read usually costs 1 unit and a write 50 ([getting started](https://developers.google.com/youtube/data/getting-started)).
- Quotas reset at midnight Pacific time ([quota costs](https://developers.google.com/youtube/data/determine_quota_cost)). They belong to the project, so every channel your app uploads for shares the same 100.
- More quota takes a compliance audit and the extension form ([quota and compliance audits](https://developers.google.com/youtube/v3/guides/quota_and_compliance_audits)).
- A channel can also hit its own limit: `uploadLimitExceeded` means the user "has exceeded the number of videos they may upload" ([videos.insert](https://developers.google.com/youtube/data/reference/rest/v3/videos/insert)). The number is not published.

## X

- Creating a post (`POST /2/tweets`) allows 100 requests per user in 15 minutes and 10,000 per app in 24 hours. Media upload has its own, higher limits ([rate limits](https://docs.x.com/x-api/fundamentals/rate-limits)).
- Rate limits and billing are separate: you can be inside the limits and still pay for usage (same page).

## LinkedIn

- LinkedIn does not publish its standard limits. Each endpoint has a daily limit per app and per member, reset at midnight UTC, and you see yours in the Developer Portal, under your app's Analytics tab, once you have called that endpoint that day ([rate limits](https://learn.microsoft.com/en-us/linkedin/shared/api-guide/concepts/rate-limits)).
- Developer admins get an email when the app passes 75% of a limit, one to two hours late, and only for app limits, not member limits (same page).

## Pinterest

- Creating a Pin is in the `org_write` category: 300 requests a day per app on Trial access, 100 a minute per user per app on Standard ([rate limits](https://developers.pinterest.com/docs/reference/rate-limits/)).
- Every call also counts toward a universal limit: 1,000 a day on Trial, 100 a second per user per app on Standard (same page). Pinterest says all of these are "subject to change without notice".

## Google Business Profile

The APIs default to 300 requests a minute, and the limits page lists no quota for local posts. Location edits are capped at 10 a minute per profile ([usage limits](https://developers.google.com/my-business/content/limits)).

## Read the limit before you hit it

Instagram and Threads tell you how much of the daily cap an account has used. Ask before each publish, not after an error:

```bash title="Threads: posts, replies and deletions used in the last 24 hours"
curl -s "https://graph.threads.com/v1.0/$THREADS_USER_ID/threads_publishing_limit?fields=quota_usage,config,reply_quota_usage,reply_config,delete_quota_usage,delete_config&access_token=$THREADS_TOKEN"
```

The Instagram call is the same shape, on `content_publishing_limit` ([our Instagram guide](/guides/how-to-post-to-instagram-via-api/) shows it). Each `config` has a `quota_total` and a `quota_duration` in seconds ([overview](https://developers.facebook.com/documentation/threads/overview)).

Meta also reports call usage on every response. `X-Business-Use-Case-Usage` gives `call_count`, `total_cputime` and `total_time` as percentages, and `estimated_time_to_regain_access` in minutes once you are throttled ([rate limiting](https://developers.facebook.com/docs/graph-api/overview/rate-limiting)):

```bash title="Meta: see the usage headers on any call"
curl -s -D - -o /dev/null "https://graph.facebook.com/v26.0/$PAGE_ID?fields=name&access_token=$PAGE_TOKEN" | grep -i "usage"
```

X and Pinterest send the limit, what is left and the reset in headers: `x-rate-limit-limit`, `x-rate-limit-remaining` and `x-rate-limit-reset` (a Unix time) on X ([rate limits](https://docs.x.com/x-api/fundamentals/rate-limits)), `x-ratelimit-limit`, `x-ratelimit-remaining` and `x-ratelimit-reset` on Pinterest ([rate limits](https://developers.pinterest.com/docs/reference/rate-limits/)).

## When you hit one

| Network | Error | What it means | What to do |
| --- | --- | --- | --- |
| Instagram | `9` / `2207042` | The account reached its daily publishing limit | Try the next day ([error codes](https://developers.facebook.com/documentation/instagram-platform/instagram-graph-api/reference/error-codes)) |
| Instagram | `4` / `2207051` | Meta thinks the publish is spam. It looks like a rate limit and is not one | Stop publishing that post and check the content (same page) |
| Meta | `4`, `17`, `32`, `613` | App, user, Page or custom call limit | Back off; the usage header says for how long ([rate limiting](https://developers.facebook.com/docs/graph-api/overview/rate-limiting)) |
| Meta | `80001`, `80002` | Page or Instagram call limit (Business Use Case) | Same |
| TikTok | `spam_risk_too_many_posts` (403) | The creator reached the daily cap, perhaps through another app | Stop. The creator can still post from the TikTok app ([direct post](https://developers.tiktok.com/doc/content-posting-api-reference-direct-post)) |
| TikTok | `rate_limit_exceeded` (429) | Over the per-minute limit | Back off (same page) |
| YouTube | `quotaExceeded` (403) | The project's daily quota is spent | Stop until midnight Pacific ([errors](https://developers.google.com/youtube/v3/docs/errors)) |
| YouTube | `uploadLimitExceeded` (400) | The channel uploaded too much | Try later for that channel only ([videos.insert](https://developers.google.com/youtube/data/reference/rest/v3/videos/insert)) |
| X | 429, code 88 | "Rate limit exceeded" | Wait until `x-rate-limit-reset` ([rate limits](https://docs.x.com/x-api/fundamentals/rate-limits)) |
| LinkedIn, Pinterest | 429 | Over a limit | Back off, and check the Analytics tab or the headers |

Three rules cover most of it:

- **A daily cap is not an error to retry.** Hold that post until the window has room, and let the account's other work and other accounts carry on.
- **Count before you publish.** Meta asks apps to enforce the publishing limit themselves, especially when they schedule posts ([content publishing](https://developers.facebook.com/documentation/instagram-platform/content-publishing)). Leave a margin: counters lag.
- **A project quota is shared.** One busy account can spend YouTube's 100 uploads or LinkedIn's daily app limit for every other account, so ration it per account.

## Where Rizamo fits

If you publish to a few accounts of your own, these limits rarely matter, and the raw APIs are the simplest choice. They start to matter when an app or an agent posts for many accounts on a schedule. Rizamo is a social media API and MCP server built for that: it counts each account's posts against the network's cap before sending, holds a post that would go over until there is room instead of failing it, and backs off when a network says slow down, without repeating a publish blindly.

Rizamo is open: [start free](https://app.rizamo.com/sign-up). Free for 2 social accounts, with unlimited posts, profiles, seats and agents, and the API and MCP included. No card. Which networks it supports today: [channels](/channels/).
