How Long Does Social Media App Approval Take? One Vendor Finally Put a Number on It
- Self-hosting a posting tool makes you the developer: each platform must register and review your app before you can publish through it.
- Postiz states it plainly on its pricing FAQ — Facebook, Instagram, Threads and YouTube "are more complicated and can usually take more than a month".
- That waiting period is the hidden cost of "free" self-hosted tooling, and it is the line item nobody budgets because it is measured in weeks, not dollars.
- Sequence it correctly: submit the reviews first and build while you wait, rather than finishing the build and then discovering the queue.
This question has always had the same unsatisfying answer — "it depends" — because platforms do not publish review SLAs. So it is worth recording when a vendor puts an actual number on it.
Postiz, an open-source scheduler, says this in the FAQ on its own pricing page (checked 2026-09-15), about getting social apps approved:
"Facebook, Instagram, Threads and YouTube are more complicated and can usually take more than a month"
What makes this useful is who is saying it. Postiz is arguing against its own free option being free. A vendor telling you the cheap path has a hidden cost is unusually good evidence that the cost is real.
Why you are suddenly a developer
People self-host a scheduler expecting to save a subscription. What they often do not expect is the role change that comes with it.
When you use a hosted tool, the vendor's app is the registered developer application. Their review passed, once, years ago, and every customer publishes through it. When you self-host, there is no vendor app — there is your app, and it needs to go through the same door.
| Hosted | Self-hosted | |
|---|---|---|
| Who is the registered developer? | The vendor | You |
| Who passes app review? | Already done | You, per platform |
| Who owns the API credentials? | The vendor | You |
| Who pays platform API usage? | Bundled in the price | You, directly |
| Time to first post | Minutes | Potentially over a month |
Not every platform is the same door
The quoted sentence names four specifically, which implies the others are easier. That matches what the developer documentation looks like across the category:
- The hard four (named by Postiz): Facebook, Instagram, Threads, YouTube. Expect a month or more.
- Middle: platforms with a review process that is lighter, or where a basic tier is available without full review.
- Easiest: platforms with open or near-open APIs, where you can be posting the same day.
The practical consequence is that your platform list determines whether self-hosting is viable at all. If you only need X, Mastodon, Bluesky and LinkedIn, the approval problem largely disappears. If Instagram is on the list, it dominates your timeline.
The other cost that arrives with the credentials
Approval is the time cost. There is a money cost attached to owning your own credentials, and 2026 made it sharper: X closed its free API tier to new developers on 2026-02-06, moving to usage-based pricing.
How much? One competitor now prints the pass-through rates on its pricing page — roughly $0.005 per request for reads and up to $0.200 per request for posts containing URLs, passed through at exact cost with no markup. Self-host, and that meter bills you rather than your vendor.
Self-hosting does not delete the bill. It splits it into three: a server, a queue you wait in, and platform API usage you now pay directly.
The category-wide version of this is in Who Is Paying for the X API Now?.
How to sequence it so the wait costs you nothing
- Write your platform list first. Before any technical work.
- Submit the hard four immediately, on day one, before the software is finished. The queue runs whether you are ready or not.
- Build against the easy platforms while you wait. You will have a working system on some networks within days.
- Budget the API usage for anything metered, especially X.
- Re-evaluate at the end. If approvals stall and the hosted option is $29–$99 a month, the arithmetic may have changed while you waited.
Step 2 is the one that converts this from a blocker into a background process. Almost everyone does it in the wrong order and discovers the queue at the end.
The route that skips app review entirely
Worth naming for completeness: publishing through your own logged-in browser session does not involve a developer application at all, because there is no API call to authorise. No review, no credentials, no per-request billing.
It has different costs — a machine that stays on, and pacing you have to get right so that automated activity does not look mechanical. That is the architecture NoobClaw uses, with per-account fingerprint-isolated profiles and your own sessions. It is not better in the abstract; it is a different set of trade-offs, compared side by side in API vs browser automation.
How to write a submission that clears faster
Review time is partly queue and partly you. The queue you cannot influence; the rest you can, and most rejections are administrative rather than technical.
Describe a user, not a feature
Reviewers are checking that a real person benefits in a way consistent with the permission you asked for. "Allows users to schedule posts to their own Page" clears faster than "integrates the Pages API" — one describes a use case, the other describes plumbing.
Request the minimum scope
Every extra permission is another thing to justify and another way to be sent back. Ask for what you will use in the first version, and add later. A narrow request reviewed once beats a broad request reviewed three times.
Record the screencast showing the permission in use
Where a demonstration is required, it must show the exact flow the permission enables, end to end, including the consent screen. A video that shows your dashboard but never shows a post being published is the single most common reason for a return.
Have the supporting pages live first
A reachable privacy policy and terms page, at stable URLs, before you submit. This sounds trivial and it accounts for a meaningful share of rejections.
Treat app review as a document you write carefully, not a form you fill in. The queue is fixed; the number of times you go through it is not.
Two more things worth knowing. First, permission scopes change over time, which means an approved app is not approved forever — a platform tightening a scope can send you back through review with no warning. Second, some vendors sell app-approval assistance as a separate service precisely because it is a specialised, repetitive task; if the wait is blocking revenue, buying that is a legitimate option rather than an admission of defeat.
If you are weighing this whole path against simply subscribing, the same-day cost comparison is in Postiz open source vs paid, and the broader open-source ledger in this piece.
FAQ
Can I use a self-hosted scheduler before approval comes through?
For platforms not requiring review, yes, immediately. For the hard four, no — the integration cannot publish until the app is approved. This is why the platform list determines the timeline.
Do approvals ever get rejected outright?
Yes, and the common causes are administrative rather than technical: unclear use-case description, missing privacy policy, or a demo that does not show the requested permission being used. Treat the submission as a document you write carefully, not a form you fill in.
Is it cheaper overall to self-host?
Only if your platform list avoids the hard four, your channel count is high, and your time is not the scarce resource. At low channel counts, a month of waiting plus a server plus API usage usually loses to a $29 subscription. The full comparison is in Postiz open source vs paid.