toreel · Publishing
Where the reels go
Automate your Instagram Reels workflow
Making the reels is the easy half. Getting them out of your computer and into four feeds is where most automation projects quietly stop.
Where toreel is
Instagram Reels publishes today, through its own Graph API integration. TikTok, YouTube Shorts and Facebook Reels are being connected, in that order, with Threads and Pinterest behind them. The queue itself is already network-agnostic: it holds a scheduled time per reel and hands the batch to whatever can post it.
I built the video pipeline and then spent six weeks on app review.→ The reviews are passed once, by whoever built the tool. You connect with an ordinary sign-in.
It posted fifteen times and the reach collapsed.→ A batch is spread across the posting day on an hour pattern, each reel on its own minute.
My TikTok integration worked and nobody ever saw a post.→ Before the audit passes, TikTok makes every API post private. It is the failure that looks like success.
I have no idea which of them worked.→ Views, reach, watch time and saves come back attached to the reel that earned them.
If you write your own
Every social network will let software post on your behalf. None of them will let it happen quickly. What follows is what each one actually asks for — useful whether you use toreel or write your own.
| Network | The gate | Wait | The catch |
|---|---|---|---|
| Instagram Reels | App Review for instagram_content_publish, behind a verified business | 2–4 weeks | Meta wants registration documents, a privacy policy, a data-deletion route and a screencast of the whole flow. Free to submit; the delay is the price. |
| TikTok | Content Posting API audit, on top of developer signup | weeks | Until the audit passes, everything your software posts is visible only to its author. Not rejected — posted, and private. A pipeline that looks like it works and publishes to nobody. |
| YouTube Shorts | API project audit | weeks | Until the project is verified, every upload through videos.insert is forced to private — whatever the volume. The daily upload allowance is generous enough for fifteen a night; it is the audit, not the quota, that stands in the way. |
| Facebook Reels | Shares Meta's review with Instagram | none, if Instagram passed | One submission covers both surfaces. If Instagram is approved this is close to free. |
| Partner approval and a contract | indefinite | Vertical video does not live there anyway. | |
| X | Paid per action | same day | Around twenty cents to post with a link — three dollars per subject per account, on the platform where short video performs worst. |
Instagram Reels
Publishing needs the instagram_content_publish permission, which needs App Review, which needs a verified business behind it. Meta asks for registration documents, a privacy policy, a data-deletion route, and a screencast showing the whole flow end to end — someone connecting an account, something being posted, the post appearing.
Reckon on two to four weeks if it passes first time, longer if it does not. The review is free; the delay is the price.
YouTube Shorts
Two separate things, and this page had them confused. The quota is the easy half: uploads bill against their own daily allowance rather than the general one, which leaves room for far more than fifteen a night.
The hard half is the same shape as TikTok's. Every video uploaded through
videos.insert from an API project that has not passed an
audit is forced to private — not throttled, not rejected,
private — and that applies at any volume, not just a large one. The audit
is the gate; the quota extension form is a separate errand behind it.
YouTube's
own reference says so, checked 16 Sep 2026.
Two that are not worth it
LinkedIn keeps posting behind partner approval and a contract; vertical video does not live there anyway. X charges per action — around twenty cents to post with a link, which on a night's batch runs to a few dollars per subject per account, for the platform where short video performs worst.
The shortcut, and what it costs
Aggregators exist precisely because of the above: they pass the reviews once, for themselves, and you connect through them with an ordinary sign-in. The protocol underneath is the same OAuth — what you are buying is not access, it is not having to wait.
The catch is worth naming. Your accounts are attached to their approved application, so leaving means reconnecting everything, and their outage is your outage. For a first month it is a reasonable trade. For a product you intend to keep, the reviews are a one-time cost that then costs nothing.
When Instagram's own scheduler stops working
Meta Business Suite schedules Reels, and then sometimes does not post them. The common causes are ordinary: the connected account was switched between personal and professional, the token behind the connection expired, the audio is licensed in a way that blocks scheduled publishing, or the video sits outside the accepted length or aspect ratio and fails at the moment it was meant to go rather than when you queued it.
What they have in common is that you find out afterwards. A scheduler that fails silently is worse than no scheduler, because you stopped watching.
A queue that lives outside your machine does not fix Meta's reasons — a refused post is refused — but it does change what happens next. Each reel carries its own time, a refusal is recorded against that reel with what the API said, and the rest of the batch carries on. You wake up to fourteen posted and one with a reason next to it, not to a schedule that quietly did nothing.
A queue that posts itself
toreel is not open yet. Leave an address and you will hear the day it is.