Every list of supported networks is also a list of absences, and the absences are the interesting part. Why can a tool publish to a Google Business Profile but not to Reddit? Why is Snapchat missing almost everywhere? Why does one product list a network that another cannot offer at any price?
The answer is almost never engineering. It is access. A network that cannot be scheduled to usually has a perfectly good publishing API sitting behind a gate, and the shape of the gate decides whether anyone will ever get through it. This guide goes through the networks people ask for most, what actually stands in the way of each, and what to do in the meantime.
Four kinds of gate
It helps to sort the absences by the kind of gate, because that tells you whether to expect a change.
- A reviewed application. You file a form, a person reads it, and you may be refused. Filing is possible today.
- An allowlist. Access is opened by a named contact at the network. You cannot apply, only be invited.
- A private partnership. The integration exists in some products because it was built with the network’s own team. There is no public route.
- No API at all. Either there never was one, or it has been retired. Nothing to apply for.
A tool can plausibly add a network in group one. Group two is business development. Group three is a relationship you cannot buy. Group four is closed, and anything that appears to work there is a scraper, which is a different and much worse thing.
Reddit: approval first, and a rule that conflicts with scheduling
Reddit is the most requested missing network, and it has two separate gates that stack.
The first is approval. Reddit’s own builder policy states that access must be requested and explicitly approved before an application uses its API at all. You can still register an OAuth client in Reddit’s settings, which is why people assume access is open, but a client you created yourself gives you credentials, not permission.
The second is commercial use. Reddit’s data API terms require a separate agreement for commercial purposes, and specifically forbid deriving revenue from providing access to the API without written approval. A paid product that includes Reddit scheduling in its plans is doing exactly that, so it needs that agreement before the first call. Reddit publishes no rate card and no timeline, and the commercial application form asks what your data budget is, which tells you what kind of conversation it is.
There is a third thing worth knowing even if the gates opened tomorrow. Reddit’s policy names posting identical or substantially similar content across subreddits as prohibited spam behavior. That is the single most obvious thing someone would want a scheduler for, so a Reddit feature would have to actively prevent its most popular use.
What to do. Treat Reddit as a channel you participate in rather than publish to. It rewards presence in a few communities, answering questions in your own voice, far more than it rewards a schedule. Keep it in your plan as a weekly reminder, not as a scheduled post.
Snapchat: real endpoints, an invitation-only door
Snapchat’s situation is the opposite of what most people assume. Server-side organic posting is not impossible there. Snapchat documents publishing endpoints for stories, saved stories and spotlights on business profiles, taking an uploaded media reference, and spotlights go through an approval step before going live.
The gate is access. Snapchat’s own getting-started documentation states that the public profile API is allowlist only, and access is requested by emailing your Snapchat point of contact with your client id and a description of the intended use. That is a named relationship, not a form, and the error path for unavailable features points callers at their partner manager.
A separate Snapchat product, the creative kit, is genuinely open, but it is a mobile component that hands content to the Snapchat camera for a person to finish and post themselves. It cannot schedule anything, so it is not an alternative.
Nextdoor: a reviewed form, and the best bet on the list
Nextdoor is better than its reputation. Its developer portal documents a real publishing API: create, edit and delete posts and comments, read your own posts, discover which profiles a token may post as, and separate endpoints for agency and event posts.
The gate is a reviewed application. Nextdoor says plainly that access is not self-service, that every application is reviewed individually against its current programme criteria, and that approval is granted case by case and is not guaranteed. No timeline is published.
Of all the gated networks, this is the one where the API genuinely does the job and the gate is a form rather than a negotiation. For a local business, Nextdoor’s open alternative is a share button, and a share button is not a schedule.
Medium and Substack: one closed, one private
These two look similar from outside and are completely different inside.
Medium’s write API is retired. Medium’s own API documentation opens by saying it is no longer supported, and Medium does not issue new integration tokens or permit new integrations. Old tokens still answer, which is why the endpoints appear alive, but there is no way for a new integration to obtain one. There is also precedent for those old tokens being revoked without notice. Medium is closed, and unlike the others there is nothing to apply for.
Substack’s API is real but not open. Where a product offers Substack Notes scheduling, that channel was built together with Substack’s own team. There is no public developer portal, no published write API and no application form. The accurate statement is narrower and more useful than either rumor: an API exists, and it is not available to new integrations.
That distinction matters when you are comparing tools. A network one product has and another does not is sometimes a difference in what each was invited to build, not a difference in capability. Which is also why nobody should list a network as coming soon on the strength of someone else having it.
| Network | The gate | Can a tool act on it? |
|---|---|---|
| Approval before access, plus a commercial agreement | A form can be filed; it is a negotiation, not a switch | |
| Snapchat | Allowlist, opened by a Snapchat contact | No application exists. Relationship work only |
| Nextdoor | Reviewed application, case by case | Yes. The most promising form on this list |
| Substack | Private partnership | No public route |
| Medium | Write API retired, no new access issued | Nothing to apply for |
| VK | New apps cannot post to a wall in practice | Unreliable even where permitted |
| Lemon8 | No developer programme of any kind | Nothing exists. Anything working is a scraper |
| Messaging only: no feed, Status or Channel publishing | Genuine as an inbox, never as a composer | |
| Twitch | No channel feed exists to post to | Schedule and clips are reachable; posts are not |
The two that are not social feeds at all
Two of the most requested are requested on a misunderstanding.
WhatsApp has a well documented business API, and it is a messaging API. It sends text, media and interactive messages to a customer who has written to you, with templates for anything outside the service window. There is no third-party publishing to Status, and WhatsApp Channels have no public write API. So an honest WhatsApp integration is an inbox integration: inbound customer messages arriving beside your comments and reviews, replies going back the same way. It should never appear in a composer, because there is nothing to compose to.
Twitch has no channel feed. The feature was retired years ago and not replaced, and the API has no endpoint for one. What is reachable is a streamer’s schedule (readable and writable), clips, channel information and follower counts. That makes Twitch a legitimate analytics and schedule-sync integration and not a publishing destination. Forcing a schedule segment through a post model would mislabel an event as a post.
VK and Lemon8: two ways of being closed
VK is the messiest case. Posting to a community wall requires a community token with wall rights, and posting to a personal wall needs a permission VK grants only by manual request. More to the point, developers report that tokens issued to recently registered apps cannot perform wall posting at all, returning an error that the method is not available for the profile type. Even setting the technical state aside, VK brings data-residency and sanctions exposure that most products should not take on for a network their customers are not asking for.
Lemon8 has no developer programme and no public API. Everything available is unofficial scraping, and several of the scraping tools say in their own descriptions that they are not affiliated with or authorized by the platform. Scraping someone’s feed in order to publish into it is not an integration. It is a terms violation with your account as the collateral, and the account that gets banned is yours, not the tool’s.
The counter-example: what an open network looks like
It is worth seeing one that passes cleanly, because it shows what all of the above is missing.
Farcaster is an open protocol. There is no app review, no allowlist and no commercial gate. Permission comes from the account holder directly: they approve a signing key for an application in their own client, and from then on that application can post on their behalf. Nobody can withhold that approval on their behalf, and nobody can revoke it except them. The publishing call takes text, a couple of embedded links, an optional channel and an idempotency key, and the limits are written into the protocol’s own specification rather than announced in a blog post.
That is the difference between an open network and a gated one. Not a better API, just permission that belongs to the user instead of to a partnerships team.
What to do about the gaps
A network your tool cannot post to is not a reason to skip the network. It is a reason to handle it differently.
Decide whether it is worth a channel at all
Be honest about whether your customers are there. A gated network you cannot schedule to and whose audience is not yours is a hobby, not a channel.
Plan it in the same session as everything else
Write those posts when you write the rest. The planning is where most of the value is, and it does not need an API. Our guide to a social media content calendar covers the weekly session.
Keep a reminder in the calendar, not a scheduled post
A calendar entry that says “post this in the community forum, Tuesday 9am” does the job. What you lose is the automation, not the plan.
Adapt the post to the culture, not just the limit
Manual channels tend to be the ones with the strongest community norms. Reddit and Nextdoor both punish copy that reads as broadcast. Write those by hand and mean it.
Measure them by hand too
A monthly note of what you posted and what came back is enough. Without it, a manual channel quietly becomes a channel nobody reviews.
Why the honesty matters
A supported-networks list is a promise, and the temptation to pad it is obvious. The cost of padding it is a channel that shows as connected and fails every publish, which is worse than a channel that was never offered.
So when a tool tells you it cannot do something, that is usually the most useful sentence in the comparison. The question to ask next is not whether the network is on the list, but what the tool will do when a network changes the rules. Our guide to why scheduled posts fail covers that from the other direction, and what each network accepts when you publish sets out the rules for the networks that are genuinely open.



