Free Social Media Posting API: Four Meanings of "Free", and the Ceilings Each Platform Actually Publishes

You wire up a posting API because it is free, and three weeks later you discover that the free part was never the expensive part. The ceiling was somewhere else: in a review queue, in a per-day counter, or in a subscription belonging to the person whose account you are posting to.

"Free social media posting API" is a single search phrase sitting on top of four different bargains. Sorting out which one you are being offered takes about ten minutes, and it is the difference between a pipeline that scales and one that quietly stops at post fifteen.

The four things "free" can mean here

• Free to call, metered by the platform. The platform charges nothing per request but publishes a hard rate ceiling. Your cost is engineering around the ceiling, not money.
• Free tier from a vendor sitting in front of the platform. You get a key and a small monthly request budget. The platform ceiling still applies underneath, so you inherit two limits stacked.
• Free as in open source, self-hosted. No subscription. The bill moves to your own credentials, your own review submissions, and your own time.
• Free to sign up, gated by app review. The endpoint is documented and free, but nothing reaches a real audience until a human approves your app - and for several platforms that review is measured in weeks.

Only the first of these has a number you can plan against on day one. The rest have a number you discover later.

The ceilings that are actually published

Threads is the clearest of the lot, and it has now read identically on four consecutive daily checks, the latest on 2026-09-21:

"Threads profiles are limited to 250 API-published posts within a 24-hour moving period." · "Threads profiles are limited to 1,000 replies within a 24-hour moving period." · "Calls within 24 hours = 4800 * Number of Impressions" · "Carousels count as a single post."

Note the third line, because it is a shape most people have never seen on a rate limit: your call budget is a function of your own reach. A profile nobody sees gets a small budget. That is a ceiling you cannot engineer past, only grow past.

X publishes posting rate limits in two places at once - an application-level allowance measured per 24 hours and a user-level allowance measured per 15 minutes, with the widely cited pair being 10,000 per day and 100 per fifteen minutes on the posting endpoint. Those figures are from our 2026-09-19 capture and were not re-fetched today, so treat them as recent rather than same-day.

What we did re-fetch today is the media side, and it contains the single most useful sentence in this whole topic:

"Limits follow the authenticated user's X Premium / verified status and media_category, not your developer API plan."

Read that twice if you have ever been told to upgrade an API tier to post longer video. Default accounts post video up to 20 minutes and 8 GB; Premium or verified accounts post up to 125 minutes and 16 GB. Direct message video is unchanged at 140 seconds and 512 MB by default, ten minutes and 1 GB on Premium. Exceed the cap and you get a 403 reading This user is not allowed to post a video longer than N minutes. The lever is a consumer subscription on the posting account, not your developer invoice. We broke the three separate product surfaces apart in X API Video Upload Limit: three official numbers, all correct, and the chunked upload paths themselves moved to v2, covered in X API Media Upload v2.

On the vendor layer, a free API tier typically buys you one key and a small monthly request budget, and the interesting detail is that the short-window cap often does not improve with money at all - one scheduler we re-checked today runs an identical 15-minute ceiling across all three of its tiers, while only the 24-hour and 30-day budgets scale. If your workload is bursty, paying more buys you nothing. That table is unpicked in Buffer API Pricing and Rate Limits.

The number we are not printing

There is a figure about unaudited TikTok clients that circulates in roughly every article on this subject. We are not repeating it, and the reason is worth stating plainly: we have tried to source it from TikTok own documentation on eight separate passes and never found the original sentence. The developer changelog does not carry it. Until we can quote the page it lives on, it stays out of our tables.

What TikTok does say in its own developer documentation is something more useful anyway, and it reframes the whole question: the Content Posting API is not positioned as a way to post to accounts you own. We walked through that wording and what it implies for anyone planning a self-serve pipeline in TikTok's API says out loud that it is not for posting to your own accounts, and the practical two-limit version in How to get the TikTok Content Posting API.

If that feels like a small distinction, it is not. Most people searching for a free posting API are trying to publish their own content to their own accounts. On some platforms that is what the API is for. On others, the API exists for a different customer entirely, and you are trying to hold a door open that was built to swing the other way.

Self-hosting moves the ceiling, it does not remove it

The open-source route genuinely removes the subscription. It does not remove the platform. One self-hosted vendor puts this on its own pricing page with unusual candour:

"Mixpost allows you to connect unlimited social accounts and manage as many clients as you need - without restrictions. However, social networks like Facebook, LinkedIn, and TikTok may impose rate limits. If you reach a platform's limit, you can request a higher limit directly from them, though some may charge a fee for this."

That is the whole self-hosting trade in three sentences. You stop paying a vendor and start dealing with the platforms yourself - including, potentially, paying them. A second open-source vendor states that app approval for Facebook, Instagram, Threads and YouTube "can usually take more than a month", and separately that you are not obliged to pay it for approval help. So the cost is time first, and only money if you want to skip the time. The longer version is in Postiz Open Source vs Paid.

There is also a third route that sidesteps API review altogether, which is to drive a real logged-in browser session on your own machine rather than asking a platform for programmatic posting rights. That is the approach NoobClaw takes for the platforms that have no usable publishing API - the accounts stay yours, the credentials never leave the device, and what you trade away is the neatness of a documented endpoint. It is a different shape of constraint, not an absence of one.

Questions worth settling before you write any code

Which platform has the most usable free posting API right now?

On published numbers alone, Threads is the easiest to reason about: the ceilings are stated in plain units, carousels are explicitly counted as one post, and the figures have held steady across four consecutive daily checks. The catch is the impression-linked call budget, which means a brand-new profile starts small by design. Compare that to platforms where the ceiling is fine but the app review gate is measured in weeks, and "usable" starts to mean "how fast can I get to my first real post", not "how many can I send".

Do rate limits reset on a clock or on a rolling window?

Rolling, on the platforms quoted above - the wording is "within a 24-hour moving period", which means there is no midnight at which your counter empties. This matters more than it sounds: a batch job written against a fixed daily reset will work for one day and then start colliding with its own previous run. Design for a rolling window even where you think the reset is fixed, because it costs nothing and the failure mode is silent.

Does paying for a higher API tier let me post longer video?

On X, explicitly not - the documentation says the limits follow the authenticated user Premium or verified status and the media category, not your developer plan. So the fix for a rejected long upload is a subscription on the account doing the posting, not an upgrade on your developer account. Check which account is authenticated before you spend anything, and expect a 403 that names the permitted duration when you get it wrong. For the platform-side free tier situation on X more broadly, see X API Free Tier Limits in 2026.