Social provider availability, format, and status matrix

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

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 availability and proof matrix reviewed 2 September 2026

Provider	Native path	Account or app boundary	Naasher ordinary access	Proof to retain
ProviderFacebook	Native pathMeta Business Suite for Pages	Account or app boundaryPage access and required grant	Naasher ordinary accessAvailable for eligible Pages	Proof to retainProvider post ID and visible Page post
ProviderInstagram	Native pathInstagram or Meta Business Suite	Account or app boundaryEligible professional account; media container must finish	Naasher ordinary accessAvailable for eligible professional accounts	Proof to retainContainer status, publish result, visible post
ProviderTikTok	Native pathTikTok web/app scheduling where shown	Account or app boundaryDirect Post needs video.publish approval and audit	Naasher ordinary accessUpload to creator inbox; Direct Post disabled	Proof to retainpublish_id, inbox handoff, then creator-completed remote post
ProviderSnapchat	Native pathSnapchat native publishing	Account or app boundaryPublic Profile API allowlisting	Naasher ordinary accessOrdinary production publishing blocked	Proof to retainNative post; no third-party success claim
ProviderLinkedIn	Native pathNative member/Page scheduler	Account or app boundaryMember identity or eligible Page administrator	Naasher ordinary accessAvailable for authorized profiles and Pages	Proof to retainPost URN and visible member/Page post
ProviderX	Native pathNative web scheduling where available	Account or app boundaryDeveloper write access; metered API operations	Naasher ordinary accessAvailable; thread parts are sequential requests	Proof to retainEach post ID and remote thread order
ProviderThreads	Native pathThreads/Instagram identity	Account or app boundaryThreads profile tied to Instagram authorization	Naasher ordinary accessAvailable for eligible profiles	Proof to retainContainer/publish result and visible thread
ProviderBluesky	Native pathNative client	Account or app boundaryDedicated app password or session	Naasher ordinary accessAvailable for supported text, images, and threads	Proof to retainRecord URI/CID and visible post
ProviderMastodon	Native pathInstance web/app	Account or app boundaryInstance policy, OAuth, and local limits	Naasher ordinary accessAvailable on compatible instances	Proof to retainStatus 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.