Installation
Install Social SDK, keep credentials server-side, and select only the integration modules your application uses.
Social SDK targets server-side TypeScript applications on Node.js 22.12 or later (including Node.js 24) and Bun. The package is ESM-only: import it with import, from an ES module ("type": "module" or .mts). It has no CommonJS build. Keep platform access tokens, managed-provider keys, OAuth client secrets, and webhook secrets out of browser bundles.
Install the package
npm install @opencoredev/social-sdkpnpm add @opencoredev/social-sdkyarn add @opencoredev/social-sdkbun add @opencoredev/social-sdknub add @opencoredev/social-sdkaube add @opencoredev/social-sdkImport the core client from the package root. Import each direct integration or managed backend from its documented subpath so unrelated adapters do not enter the application bundle.
Check your setup
Run social-sdk doctor --adapter <name> after installing to confirm that the selected adapter’s credentials are configured. It checks your local environment only, lists the names of missing variables without printing their values, and never contacts a platform or managed backend. Like every CLI command, it sends one anonymous usage event; turn that off with social-sdk telemetry disable or DO_NOT_TRACK=1 (see CLI telemetry). social-sdk version prints the installed version. See the diagnostic CLI for every command.
Choose the first route
- Start with the deterministic testing backend when you are building the application flow or running CI.
- Use a direct integration when the application already has suitable platform credentials or will own the platform authorization flow.
- Use Zernio, Post for Me, PostFast, Postiz, or Buffer when the application will use that provider’s connection and execution service.
Managed services are optional. A direct integration does not require a Zernio, Post for Me, PostFast, Postiz, Buffer, or Social SDK account. A managed integration uses the developer’s own provider account and may create provider charges.
Runtime boundary
Create clients inside trusted server code. A browser may send an authenticated application request that names content and an application-owned account selection, but it must not receive backend credentials or an unrestricted connected-account reference.
Next, use the quickstart to verify your application without external side effects, then choose an integration.