GuidesSocial provider availability, format, and status matrix
Check native fallbacks, account requirements, supported formats, approval boundaries, and the remote status that proves a publishing attempt finished.
Last updated October 17, 2026 · 8 min read · The Naasher team · Editorial and corrections policy (Arabic) · اقرأ بالعربية
Answer first: classify every target by four separate facts: account eligibility, format acceptance, app-level production approval, and final remote status. “Connected” proves authorization, not that a future post or every format can publish.
Operating matrix
Access wording reviewed 17 October 2026. Check the provider choices shown in your account before buying or moving a queue. Facebook, Instagram, Threads, LinkedIn Pages, and YouTube can remain limited to approved testers while app review is pending. A paid plan cannot remove that restriction.
The primary provider references below were reviewed on 2 September 2026. Provider rules are volatile; re-open the linked source and check the account UI before a launch. A source review is not a receipt that a specific third-party app has production approval.
| Provider | Native path | Account or app boundary | Naasher ordinary access | Proof to retain |
|---|---|---|---|---|
| Meta Business Suite for Pages | Page access and required grant | Check connection eligibility; app-review restrictions may apply | Provider post ID and visible Page post | |
| Instagram or Meta Business Suite | Eligible professional account; media container must finish | Check connection eligibility; app-review restrictions may apply | Container status, publish result, visible post | |
| TikTok | TikTok web/app scheduling where shown | Direct Post needs video.publish approval and audit | Upload to creator inbox; Direct Post disabled | publish_id, inbox handoff, then creator-completed remote post |
| Snapchat | Snapchat native publishing | Public Profile API allowlisting | Ordinary production publishing blocked | Native post; no third-party success claim |
| Native member/Page scheduler | Member identity or eligible Page administrator | Profiles and Pages have separate grants; verify Page access | Post URN and visible member/Page post | |
| X | Native web scheduling where available | Developer write access; metered API operations | Available; thread parts are sequential requests | Each post ID and remote thread order |
| Threads | Threads/Instagram identity | Threads profile tied to Instagram authorization | Check connection eligibility; app-review restrictions may apply | Container/publish result and visible thread |
| Bluesky | Native client | Dedicated app password or session | Available for supported text, images, and threads | Record URI/CID and visible post |
| Mastodon | Instance web/app | Instance policy, OAuth, and local limits | Available on compatible instances | Status ID/URL and visible status |
Primary sources and limits
- Meta: Facebook Page posts, Instagram content publishing, and Threads publishing.
- TikTok: Content Posting API get started distinguishes Direct Post approval, user authorization, audit restrictions, and asynchronous status.
- Snap: Public Profile API introduction and getting started describe the product and allowlisting path.
- LinkedIn: Posts API separates member and organization authors.
- X: Create Posts documents post and reply creation; API pricing is a developer-app cost source, not Naasher customer billing semantics.
- Bluesky: creating a post documents records and media blobs.
- Mastodon: statuses methods document status creation while each instance can apply local policy.
Format acceptance is a separate gate
Before scheduling, test one representative item for text, image, video, carousel, thread, poll, link, alt text, visibility, and first comment—only the formats the campaign needs. Mark unsupported or unverified cells explicitly. Do not convert “the provider API has an endpoint” into “this account and this tool can use it.”
Status words that are not final success
- Connected: authorization completed.
- Scheduled or queued: local work exists for a future time.
- Accepted or container created: the provider received an operation.
- Uploaded or sent to inbox: media arrived but may still require processing or human completion.
- Published: the provider returned its final success state.
- Verified: an operator can open the correct remote post on the intended identity.
A Naasher worked example
Naasher exposes the integrations available to the account, but the matrix above keeps TikTok upload and Snapchat approval limits visible. For other providers, select the exact identity, test the required format, and retain the final provider identifier. If the result is uncertain or partial, do not blindly repeat the mutation; use the symptom-first incident guide.
This matrix is a decision aid, not a provider certification. Recheck it whenever an account role, scope, app review, provider policy, or media requirement changes.
YouTube and Discord: additional connection boundaries
Section reviewed 17 October 2026. YouTube upload is implemented, but ordinary access remains restricted to approved test accounts pending OAuth scope approval. Do not plan a public YouTube campaign on the assumption that a listed integration grants access. Use YouTube Studio when your account cannot connect. The YouTube upload documentation describes the API mechanism, not Naasher's approval status.
Discord uses a verified incoming webhook for channel announcements. It is not a moderation bot or a Discord inbox; automatic mention parsing is disabled. Follow the Discord connection and delivery guide and verify the visible message before retrying. Neither a successful connection nor a queued job proves delivery.
Frequently asked questions
- Does a listed integration mean anyone can publish through it?
- No. Ordinary production access can depend on app review, account type, granted scopes, provider allowlisting, media format, and the specific user authorization.
- What status should an operator trust?
- Trust the final provider result and the visible remote post. Connected, uploaded, container created, queued, and accepted can all precede publication.
- Which providers are blocked in Naasher today?
- TikTok Direct Post is not enabled for ordinary production use and follows an upload-to-inbox path; Snapchat ordinary production publishing remains blocked pending Public Profile API approval.