What it actually takes to get publishing API access
Reading a platform's API docs makes programmatic posting look like a weekend integration. The endpoints are straightforward. The approval to use them in production is not — and that's where most projects stall.
Written for developers and AI-agent builders who need to publish on behalf of their users. Last reviewed August 2026 — platform requirements change, so always confirm against the official docs.
TikTok
video.publish / video.upload
- Gate
- Content Posting API audit
- Realistic timeline
- ~1–2 weeks for a clean first submission; longer after any rejection
What you must submit
- · A working demo video of your complete OAuth + upload flow
- · A public privacy policy URL
- · A written description of how you handle user data
- · A UX that meets TikTok's posting-consent requirements
The part that catches people out
Until you pass the audit, everything your app posts is forced to private viewing mode. You can build the whole integration, watch it return 200s, and still have nothing publicly visible. This is the detail that surprises most teams.
From someone who went through it
One developer reported being rejected because their demo video only showed first-time authorisation — the reviewer wanted to see the consent screen appear again after a token refresh. Recording the refresh path, not just the happy path, got them through on the second attempt.
instagram_business_content_publish
- Gate
- Meta App Review + Business Verification
- Realistic timeline
- ~2–4 weeks for standard permissions
What you must submit
- · Business Verification in Meta Business Manager — official business documents
- · A separate screencast per permission showing the full user journey
- · Privacy policy URL and data deletion instructions
- · An Instagram Business/Creator account linked to a Facebook Page
The part that catches people out
Publishing on behalf of accounts you don't own requires Advanced Access, which is a higher bar than standard review. That covers essentially every product that posts for its users. Without it you're capped at a handful of test users.
YouTube
youtube.upload
- Gate
- Google OAuth verification
- Realistic timeline
- Weeks, and longer if a security assessment is triggered
What you must submit
- · OAuth consent screen verification with a verified domain
- · A demo video of the upload flow
- · A privacy policy covering the sensitive scope
- · Quota that is low by default and must be requested upward
The part that catches people out
Upload quota is the quiet constraint. Access approval and enough quota to actually run a product are two different fights, and the second one is ongoing.
So what are the options?
There are three honest paths, and which one is right depends entirely on how central publishing is to what you're building.
- Apply yourself. Correct if publishing is your core product and you'll want control over quota, branding, and the consent flow. Budget a month of calendar time across the three platforms, plus rework after rejections. You will need real business documents for Meta.
- Use an approved provider. You inherit someone else's approvals and ship this week instead. The tradeoff is a dependency and a per-post or subscription cost. Several exist — QPost (this site), plus Blotato, Publora, PostEverywhere and others. Compare them on the platforms you actually need rather than headline platform counts; many pad those with networks like Bluesky, Mastodon and Telegram that have open APIs and no approval process at all.
- Don't publish at all. Genuinely worth considering. Generating a draft and handing it to the user to post takes zero approvals. If the last mile isn't the valuable part of your product, skip the whole problem.
Common questions
How long does TikTok Content Posting API approval take? ▼
Roughly one to two weeks for a clean first submission. A rejection puts you back in the queue, so budget longer if your consent UX or demo video doesn't match their spec on the first attempt.
Why are my TikTok API posts private? ▼
Until your app passes TikTok's Content Posting audit, every post it creates is forced into private viewing mode. The API returns success and the video exists, but nobody else can see it. Passing the audit is the only way to lift that restriction.
Why was my TikTok Content Posting API audit rejected? ▼
The most common cause is the demo video. Reviewers want to see the full consent journey, and one developer reported being rejected specifically because their video only covered first-time authorisation and not the consent screen reappearing after a token refresh. Record the refresh path as well as the happy path, and make sure the video shows your actual posting UX rather than a mock.
Do I need a registered business to use the Instagram Content Publishing API? ▼
In practice, yes. instagram_business_content_publish requires Meta App Review plus Business Verification, and Business Verification asks for official business documents. Publishing to accounts you don't own additionally requires Advanced Access.
Can I post to TikTok, Instagram and YouTube without my own API approvals? ▼
Yes — you can publish through a provider that already holds the approvals, so your users connect their own accounts and you inherit the provider's access. The tradeoff is a third-party dependency and a per-post or subscription cost.
Is the YouTube Data API enough to upload videos? ▼
Access is only half of it. youtube.upload is a sensitive scope requiring OAuth verification, and upload quota is granted separately and sparingly. Plenty of projects get approved and then discover their quota won't support real usage.
If you want to skip the wait
QPost holds the approvals for TikTok, Instagram and YouTube. Your users connect their own accounts, and you publish through one REST API or an MCP server — no audit, no business verification, no private-mode limbo. Free while in beta.