Possible, permitted and realistic are different questions
Every "post everywhere" promise folds three questions into one.
Possible: can software put a post on this platform at all? Nearly always yes. A script driving a browser can click any button a person can.
Permitted: does the platform's official API have a write endpoint, and do its terms let your app call it?
Realistic: can a solo founder, with one account and no compliance team, get the access that endpoint requires before launch day?
This guide answers the second and third questions for the 16 channels LaunchBeam writes launch copy for. Every platform rule below comes from that platform's own documentation, policy pages, official blog or published API repository, checked on September 10, 2026. These pages change, so re-check any rule before you depend on it.
Three tiers, defined
- Auto-post. The platform's official API accepts a post made with your credentials, and software publishes it on schedule. You don't need a tab open.
- Assisted. There is no write path you can safely use, but the platform has a compose, share or submit page that accepts a prefilled link, and sometimes the text as well. Software opens it with as much filled in as the platform allows. You paste the rest, read it and click Post.
- Manual export. There is no usable write path. Software prepares the copy, assets and a checklist, and at the right time reminds you with a link to the submit or upload page, prefilled where the platform's form allows it.
These are LaunchBeam's names (auto_post, assisted_post, manual_export in the code), but they're useful whatever tool you use. Assisted and manual are not failures. On some platforms they're the only honest options.
Automatable with your own credentials
On these platforms, an individual can get a token or URL that publishes. No app review, no business verification.
Bluesky. Bluesky's user FAQ tells you to generate an App Password in settings to log in to third-party apps. With your handle and an app password, a client opens a session over the AT Protocol and writes the post as a record. The tool never holds your main password.
Mastodon. POST /api/v1/statuses takes a user token with the write:statuses scope, issued by your own instance. It also accepts an Idempotency-Key header and remembers it for up to an hour. That header is what stops a retried request from posting twice.
Dev.to. The Forem API authenticates with an api-key header and publishes through POST /api/articles. Set published to true to go live, or leave it false and it saves a draft.
Discord. Discord's webhook docs say webhooks "do not require a bot user or authentication". The webhook URL is the credential. Add wait=true and Discord confirms the message was saved and returns it, so a silent failure can't pass as a success. The limit is scope: you need a webhook in a server you run, or one whose admin gave you one.
Telegram. The Bot API takes the bot token in the request URL, and sendMessage accepts a channel as @channelusername.
One caveat: a working token is not an audience. These channels only matter if you already have followers there.
Automatable with the right account, app or payment
The write endpoints on these platforms exist and work, but only once you've paid for access, have the right account type, or hold an app permission you have to set up or apply for.
X
X's API pricing page describes pay-per-usage with no subscriptions: you buy credits in the Developer Console and each request draws them down. The rate-limit table caps post creation separately.
| X API item | Price or limit |
|---|---|
| Create a post | $0.015 per request |
| Create a post that contains a URL | $0.20 per request |
| Post creation, per user | 100 per 15 minutes |
| Post creation, per app | 10,000 per 24 hours |
Prices and policies checked on September 10, 2026.
A launch post almost always carries a link, so the URL price is the one that matters. Say you post a six-part thread and only the last post holds the link. That's five posts at $0.015 plus one at $0.20, or $0.275 for the thread. Put the link in every post and the same thread costs $1.20. Small either way, but someone's credits pay for every request, and you should know whose.
Facebook Pages
The Pages API publishes with a Page access token. Its guide lists pages_manage_posts, pages_manage_engagement, pages_read_engagement and pages_read_user_engagement, and Meta's permissions reference adds pages_show_list as a dependency of pages_manage_posts. The person granting the token must be able to perform the CREATE_CONTENT, MANAGE and MODERATE tasks on the Page.
The catch is in Meta's access levels. Under Standard Access, an app can only request these permissions from people who have a role on that app. Serving anyone else needs Advanced Access, which requires Business Verification, and pages_manage_posts also has to pass App Review with a screencast. For a founder, the realistic route is a Meta app you create yourself, with you on it, posting to a Page you manage.
Instagram's content publishing guide sets three conditions:
- A professional account. The guide is written for professional accounts connected through the Instagram Platform.
- A publish permission.
instagram_content_publishif you sign in with Facebook Login, orinstagram_business_content_publishwith Instagram Login. - Media. Every post must be an image, video or carousel, so a text-only post isn't possible, and Instagram fetches the file itself from a publicly accessible server.
Publishing takes two calls: create a media container, then publish it. The guide caps each account at 100 API-published posts in a moving 24-hour window, with a carousel counting as one.
LinkedIn has two routes, and they're not equally easy.
- Your personal profile. Posting needs
w_member_social. The Share on LinkedIn guide says you get it by adding the Share on LinkedIn product to your app in the developer portal. That guide still documents the olderugcPostsendpoint; the Posts API, which replaces it, also acceptsw_member_social. - A company page. Posting needs
w_organization_social, and the posting member must be an administrator or content admin of the page. That permission comes with the Community Management API, which LinkedIn calls a vetted product. Its app review page says it is open only to registered legal organisations with a commercial use case. You need a verified business email, your organisation's legal details and privacy policy, and a super admin of your company page must verify the app. Approval gets you a rate-limited Development tier; Standard needs a second application with a screencast. Without a registered company, this route is closed.
Two mechanics catch people out. First, every call to the Posts API must name a Linkedin-Version in YYYYMM form. LinkedIn's versioning page says versions ship monthly and each is supported for at least a year. Its notice gave August 17, 2026 as the sunset date for the August 2025 version (202508), a date that has now passed. A hard-coded version stops working on a known date. Second, an image has to be uploaded through the Images API before the post can reference it. Multi-image organic posts go through a separate MultiImage API.
Hashnode
Hashnode's GraphQL API publishes with a publishPost mutation and a personal access token, as Hashnode's post on its API describes. Its changelog says that since May 13, 2026, every API request needs a Pro plan on the publication. Hashnode Pro costs $5 a month or $50 a year per publication, and the Pro page lists GraphQL API read and write access among its features.
Gated behind an audit: TikTok and YouTube
Both platforms have real upload APIs, and both keep uploads from an unaudited app out of public view.
TikTok. The Content Posting API needs an app approved for the video.publish scope. Content posted by unaudited clients is "restricted to private viewing mode" until the app passes an audit against TikTok's terms. There is a second route, Upload. It sends the video to the creator's TikTok inbox as a draft, and the creator finishes posting inside TikTok.
YouTube. The videos.insert reference says videos uploaded from unverified API projects created after 28 July 2020 are restricted to private viewing. The restriction lifts only when the project passes a compliance audit.
The audit applies to the app, not to you. Register your own developer app and your launch video sits private until that app is audited, which is rarely worth doing for one launch. The realistic automation is preparation: a finished caption, title, tags and a checklist, ready when you upload the file yourself.
No way to post a launch: Product Hunt, Hacker News, Indie Hackers
Product Hunt. The API docs say the API must not be used for commercial purposes by default, and that write access is granted case by case. The GraphQL schema Product Hunt publishes in its API repository has mutations for goals and following users, and none that creates a post or launch. You launch in the browser, as the maker. Timing is its own subject: see Product Hunt launch timing and the root-domain rule.
Hacker News. The official API is a Firebase feed of public HN data. Every endpoint it documents reads items, users or story lists, and none submits anything. What you can do is open the submit form with the title and URL already filled in, as HN's own bookmarklet does, so posting is one read and one click.
Indie Hackers. As of September 10, 2026 we found no documented public API for creating posts. You write it in their composer.
Here too, what you can automate is the preparation: the title, URL and first comment written in advance, and an alert at the hour you've picked. Our guide to launch directories by lead time and cost covers how far ahead each one needs planning.
Reddit: possible, and a poor default
Reddit does have a submit endpoint; its Data API wiki links technical guidance for submitting a post. The same page requires registered OAuth for every client and limits free access to 100 queries per minute per OAuth client ID.
The Responsible Builder Policy is the part to read before automating anything:
- Approval first. You have to request access and get explicit approval before using Reddit data through the API.
- Apps are labelled. Apps register a developer profile, which gives them an app label.
- No automated spam. Apps may not spam through automated posts, including identical or substantially similar content across subreddits.
- Enforcement reaches you. Reddit can revoke tokens and suspend the app, the account, and associated accounts, domains or subreddits.
Then there are the subreddits. Each sets its own rules on self-promotion, and those rules apply to your post however it was sent. Our guide to Reddit self-promotion rules for launch posts goes through that part in detail.
So assisted posting is the sensible default on Reddit. Software drafts the post and opens the subreddit's submit page. You check the subreddit's rules, paste or review the copy, read it once more, and click Post yourself.
The decision table
| Platform | Official write path | What you need | Without it |
|---|---|---|---|
| Bluesky | AT Protocol record | Handle and an app password | Post by hand |
| Mastodon | POST /api/v1/statuses |
User token with write:statuses |
Post by hand |
| Dev.to | POST /api/articles |
Your API key | Post by hand |
| Discord | Execute Webhook | A webhook URL for the channel | Post by hand |
| Telegram | Bot API sendMessage |
Bot token, a channel it can post to | Post by hand |
| Hashnode | GraphQL publishPost |
Access token, publication on Pro | No API access at all |
| X | POST /2/tweets |
Developer app, user token, prepaid credits | No API posts |
| Pages API | Page token with pages_manage_posts and related permissions |
Only people with a role on your app | |
| Container, then publish | Professional account, publish permission, hosted media | No API post, and never text-only | |
| LinkedIn profile | ugcPosts or the newer Posts API |
w_member_social via Share on LinkedIn |
Post by hand |
| LinkedIn page | Posts API | w_organization_social, registered organisations only |
No page posting through the API |
| TikTok | Content Posting API | Audited app | Posts stay private |
| YouTube | videos.insert |
Audited project | Uploads stay private |
| Submit endpoint | Approved access, OAuth, subreddit rules that allow it | Token revoked, app or account suspended | |
| Product Hunt | None for launches | Your browser | Browser only |
| Hacker News | None (read-only API) | Your browser | Browser only |
| Indie Hackers | None documented | Your browser | Browser only |
Policies checked on September 10, 2026.
A pre-purchase checklist for any scheduling tool
Before you pay for a tool that promises to publish your launch, get answers to these.
- Which API? The tool should name the official API it uses for each platform, or say there isn't one.
- Whose credentials? Your token, your app, or the vendor's app? For TikTok, YouTube or a LinkedIn company page, ask whether the vendor's app holds the audit or approval those uploads need.
- Which permission? For Facebook, Instagram and LinkedIn, the answer is a scope name. "Full access" is not an answer.
- What happens when a permission is missing? You want to hear "degrades to a prefilled composer" or "sends a reminder", not "the post is skipped".
- What happens after an ambiguous failure? If a request times out after the platform received it, does the tool retry and risk a double post, or stop and tell you?
- What happens to media it can't deliver? If the API takes one image and you attached four, is the post blocked, handed back to you, or sent without three of them?
- Do you see the outcome before you schedule? "This will publish" and "this will remind you" should be visible on the scheduling screen, not in a failure email afterwards.
- Is there an off switch? One control that stops all outgoing posts at once.
- Who pays per-request fees? On X, every post costs money. Find out whose credits a scheduled post uses.
Where LaunchBeam fits
LaunchBeam writes launch copy for 16 channels, and every connector declares its tier in code: auto-post, assisted or manual export. LaunchBeam has no X app of its own: you paste a user access token, so the developer app and credits behind it are yours. Facebook and Instagram use a token from your own Meta app. Until they're connected, LinkedIn and Facebook get an Open composer button for the platform's share dialog, with your link filled in and a Copy button for the text, and Instagram gets a reminder with the caption. The scheduling screen says which you'll get: Schedule auto-publish or Schedule reminder.
A LinkedIn post with more than one image goes to the assisted path rather than losing images two to four. That guard is LinkedIn-only for now: Facebook, Instagram, Telegram and Discord publish the first image you attach, and X, Bluesky and Mastodon auto-publish text only, which the post editor flags. A publish whose outcome is unknown becomes a reminder, not a retry that could post twice. Reddit stays assisted unless you switch on auto-post for that connection ("Risky — off by default"). Either way, the post is checked before you can schedule it: against LaunchBeam's own list of launch subreddits for everyone, and against the subreddit's live rules once a Reddit account is connected. TikTok, YouTube, Product Hunt, Hacker News and Indie Hackers get the copy, a checklist and a reminder linking to the upload or submit page.
Auto-publishing is on the paid plans. On the free trial, scheduled posts arrive as reminders and X isn't available; the pricing page has the details. A per-workspace pause stops scheduled posts and email at once while analytics keeps running, and the docs walk through the Connections page.
