![Social provider cards compared by availability, format, and final publishing status](/editorial/best-scheduling-tools-cover.webp)Guides

# Social 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 September 2, 2026 · 8 min read · The Naasher team · [Editorial and corrections policy (Arabic)](/editorial-policy) · [اقرأ بالعربية](/guides/provider-status-matrix)

Share[Share on X](https://twitter.com/intent/tweet?text=Social%20provider%20availability%2C%20format%2C%20and%20status%20matrix&url=https%3A%2F%2Fnaasher.com%2Fen%2Fguides%2Fprovider-status-matrix)[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fnaasher.com%2Fen%2Fguides%2Fprovider-status-matrix)[Share on WhatsApp](https://wa.me/?text=Social%20provider%20availability%2C%20format%2C%20and%20status%20matrix%20https%3A%2F%2Fnaasher.com%2Fen%2Fguides%2Fprovider-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](https://developers.facebook.com/docs/pages-api/posts/), [Instagram content publishing](https://developers.facebook.com/docs/instagram-platform/content-publishing/), and [Threads publishing](https://developers.facebook.com/docs/threads/posts).
- TikTok: [Content Posting API get started](https://developers.tiktok.com/doc/content-posting-api-get-started) distinguishes Direct Post approval, user authorization, audit restrictions, and asynchronous status.
- Snap: [Public Profile API introduction](https://developers.snap.com/marketing-api/Public-Profile-API/Introduction) and [getting started](https://developers.snap.com/marketing-api/Public-Profile-API/GetStarted) describe the product and allowlisting path.
- LinkedIn: [Posts API](https://learn.microsoft.com/en-us/linkedin/marketing/community-management/shares/posts-api) separates member and organization authors.
- X: [Create Posts](https://docs.x.com/x-api/posts/create-post) documents post and reply creation; [API pricing](https://docs.x.com/x-api/getting-started/pricing) is a developer-app cost source, not Naasher customer billing semantics.
- Bluesky: [creating a post](https://docs.bsky.app/docs/tutorials/creating-a-post) documents records and media blobs.
- Mastodon: [statuses methods](https://docs.joinmastodon.org/methods/statuses/) 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](/en/guides/publishing-incidents).

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.

## Test the workflow with your real accounts

Start free, then compare the composer, calendar, and channel limits with what your team actually needs before choosing a plan.

[Start free](https://app.naasher.com/sign-up)[Review pricing in Arabic](/pricing)

## 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.

## Read next

[![A publishing timeline branching into missing, duplicate, partial, and recovered outcomes](/editorial/schedule-facebook-cover.webp)GuidesIncidentsTroubleshootingDiagnose publishing incidents from the symptom firstA runbook for missing, duplicate, partial, delayed, unauthorized, and media-rejected social posts without unsafe automatic retries.September 3, 2026·7 min read](/en/guides/publishing-incidents)

[![A shared publishing calendar beside separate native network tools and a reversible decision path](/editorial/best-scheduling-tools-cover.webp)GuidesDecision guideWorkloadScheduler or native tools? A neutral decision treeChoose native network tools, a shared scheduler, or a hybrid workflow from account count, approval risk, reporting needs, and total operating effort.September 2, 2026·7 min read](/en/guides/scheduler-vs-native)

[![A controlled handover moving accounts, schedules, approvals, and evidence between tools](/editorial/social-media-approval-workflow-cover.webp)GuidesMigrationRunbookMigrate social schedulers without duplicate or lost postsInventory accounts, ownership, schedules, approvals, analytics, exports, and provider access; pilot one workspace; then cut over with a tested rollback.September 3, 2026·8 min read](/en/guides/migration-runbook)

---

Canonical URL: https://naasher.com/en/guides/provider-status-matrix