What a scheduling tool can (and cannot) post to each social network
Every scheduler works through each network's developer API, and each network decides what third-party tools may do. Here is what that means for Facebook, Instagram, LinkedIn, X, TikTok, YouTube and Pinterest.
“Why can’t I schedule to my personal Facebook profile?” “Why does my TikTok post say private?” “Why are there no numbers for my LinkedIn post?” These questions are rarely about the scheduling tool itself. Every scheduler, from the largest suite to the smallest app, publishes through each network’s official developer API, and each network decides what third-party tools are allowed to do, for which account types, and after what review. This post walks through the seven networks PostRoost supports, with links to the networks’ own developer documentation, so you can set expectations with clients before you promise anything.
Why the rules differ by network
A network’s API is a contract between the network and the developer of a tool. The network decides:
- Which accounts a tool may act for (business pages, professional accounts, personal profiles)
- Which permissions a tool must request, and which of those need a review before the public can grant them
- Which formats can be published (images, video, carousels, stories)
- Which numbers a tool may read back
- How much a tool may do per day, and sometimes what it costs
None of these are settings a tool can switch on by itself. When a scheduler says a feature “depends on network approval”, it means exactly that.
Facebook: Pages, not profiles
Meta’s Pages API documentation for posts describes publishing to Facebook Pages. A tool asks for permissions such as pages_manage_posts and pages_read_engagement, and the person who signs in must be able to perform tasks such as creating content and managing the Page. The documentation covers Pages only; personal profiles and groups are not part of it.
What this means in practice:
- Connect Facebook with an account that has the right role on the client’s Page.
- If a client only has a personal profile, they need a Page before any tool can schedule for them.
- Some permissions need Meta’s App Review before people outside the developer’s test list can grant them.
PostRoost publishes text, links, up to ten images or a video to Pages, with a first comment posted as the Page. Details: Facebook integration.
Instagram: professional accounts only
Meta’s Instagram content publishing guide is written for Instagram professional accounts. Personal accounts cannot publish through the API, which is why every scheduler asks clients to switch to a Business or Creator account first (it is free, in the Instagram app).
Two other points from that guide are worth knowing:
- Images must be JPEG. Tools that accept PNG or WebP uploads convert them before sending.
- There is a rolling 24-hour limit on API-published posts per account. The guide gives the limit and an endpoint to check current usage; it is high enough that ordinary schedules never reach it.
The API also supports Stories. PostRoost publishes photo posts, Reels and carousels of up to ten items, but not Stories. Details: Instagram integration.
LinkedIn: profiles are easy, Company Pages need approval
LinkedIn separates the two. Posting to a member’s own profile is available to any developer app with the standard sharing product. Managing Company Pages, and reading their analytics, goes through the Community Management API, which LinkedIn describes as a vetted product with a Development tier and a Standard tier. Moving to the Standard tier requires a screencast that demonstrates each use case the developer is asking for.
What this means for clients:
- A tool without Community Management approval can only post to the profile of whoever signed in.
- Post numbers for personal profiles are restricted too; the same LinkedIn page notes that the permission for member post management is closed to new requests.
- If a B2B client lives on its Company Page, ask any tool you evaluate whether it has the approval.
Our LinkedIn integration page explains how PostRoost behaves before and after that approval.
X: pay-per-use behind the scenes
X’s API pricing page describes pay-per-usage pricing: the developer buys credits in advance and each request uses some. Creating a post that contains a URL is listed separately and costs more than a plain post.
You will not see this cost directly, because the tool operator pays it, but it explains two things you may notice across tools: why some schedulers limit X posting on lower plans, and why putting the link in a reply is a common pattern. PostRoost’s price does not change with X usage; it can post your first comment as a reply straight after the main post. Details: X integration.
TikTok: private until the app is audited
TikTok’s Content Posting API guide is explicit: content posted by unaudited API clients is restricted to private viewing mode, and the client must pass an audit to lift that restriction. The same guide says that when TikTok pulls a video or photo from a URL, the URL must belong to a domain or URL prefix the developer has verified.
So if a client’s TikTok post appears as private, the question to ask is whether the tool’s app has passed TikTok’s audit, not whether a setting was missed. PostRoost publishes videos and photo posts to TikTok; read the TikTok integration page before relying on public posting.
YouTube: verification and quota
Uploading to YouTube needs a sensitive Google permission. Google’s help page on sensitive scope verification says apps requesting sensitive scopes must complete Google’s OAuth app verification before being granted access.
YouTube also has a daily quota per developer project. The YouTube Data API getting-started guide describes the default allocation, which includes a fixed number of upload calls per day, shared by everyone using that project. A high-volume video schedule may need the developer to request more quota from Google.
PostRoost uploads videos to a client’s channel at the scheduled time, with the title from the first line of the caption. Details: YouTube integration.
Pinterest: trial access first
Pinterest asks developers to request trial access for a new app; Pinterest reviews the request and replies by e-mail, and higher access levels are a separate step described in its access-tier guide. Until an app has the higher level, what it can do for other people’s accounts is limited.
PostRoost publishes image Pins with a title, description, destination link and alt text to the board you choose. The Pinterest integration page lists the current requirements.
A quick reference
| Network | Account a tool can publish to | What to check before you promise it |
|---|---|---|
| Pages | The person connecting has a role on the Page | |
| Professional (Business or Creator) accounts | The account is professional; images will be sent as JPEG | |
| Profiles; Company Pages after LinkedIn’s approval | Whether the tool has Community Management API access | |
| X | Accounts that sign in | Nothing on your side; the operator pays per use |
| TikTok | Accounts that sign in | Whether the tool’s app has passed TikTok’s audit for public posts |
| YouTube | Channels the signed-in account manages | Google verification; quota for heavy video schedules |
| Accounts that sign in, to a chosen board | The app’s Pinterest access level |
Questions to ask any scheduling tool
Whichever tool you use, these questions save awkward conversations with clients later:
- Which account types can you publish to on each network?
- Which network reviews has your app passed (Meta App Review, LinkedIn Community Management, TikTok audit, Google verification, Pinterest access)?
- Which formats are not supported (for example Stories or Shorts-specific settings)?
- Which numbers come back for each network, and which do not?
- What happens when a network rejects a post: is it retried, and where do I see the error?
A tool that answers these plainly is easier to build a client service on than one that lists every network with a tick. PostRoost’s answers are on each integration page, and if you need to know how a specific deployment stands with a network’s review, ask us.
Keep an eye on changes
Networks change their APIs regularly: new versions, new limits, retired permissions. LinkedIn, for example, versions its marketing APIs and retires old versions on a published schedule. When something that worked last month stops working, the network’s developer changelog is usually the first place the reason appears, so it is worth checking before you assume the tool is at fault.
