Model
Understand the four independent concepts that define Social SDK behavior and keep platform routing explicit for every call.
Social SDK keeps four concepts separate because combining them produces unsafe routing and misleading capability claims.
| Concept | Meaning | Examples |
|---|---|---|
| Platform | The network where activity occurs. | X, Threads, Bluesky, YouTube, TikTok, Instagram, LinkedIn |
| Backend | The configured route that executes an operation. | A direct integration, Zernio, Post for Me, PostFast, Postiz, Buffer |
| Content format | The structure submitted to an operation. | Text, image, video, carousel, document |
| Capability | An operation an integration can actually perform. | Publish, read, analytics, comment reply, message send, event verification |
An account reference records its backend instance and platform. Selecting the account therefore selects the route. The client does not scan for another backend that might accept the request.
Formats overlap. A platform can support photos and video, and one publication can contain text plus ordered media. Documentation groups integrations by useful filters without creating separate text and video SDKs.
Capabilities come from each adapter’s static manifest. social.capabilities() reads those manifests locally and makes no request, and the client checks the same manifest before dispatching an operation. Neither check knows the connected account’s scopes or eligibility; the provider reports those when the call runs.
See the architecture diagrams for the routing, grant, delivery, and webhook flows.
Each concept has its own page: accounts for connection and ownership, capabilities for declared support, content for formats and preparation, and media for attachment sources and processing.