Skip to content

TypeScript & Node.js SDK

Social media API SDK for TypeScript and Node.js

Build social publishing into application code with typed helpers around the PostSider API, or generate another client from the OpenAPI specification when your stack needs it.

Start with the social media scheduler API or browse the full developer platform.

How it works

Move from raw HTTP to typed social publishing code.

Use REST for the wire protocol and the SDK when the integration becomes part of a larger TypeScript or Node.js codebase.

01

Install the SDK

Use the official PostSider TypeScript and Node.js client when you want typed helpers around the public API instead of building every HTTP request by hand.

02

Create the client

Initialize the SDK with the credential appropriate for your application or organization and keep that secret outside your source code.

03

Call publishing methods

Work with connected channels and create publishing actions through typed application code backed by the same PostSider API.

04

Fall back to OpenAPI when needed

Use the published OpenAPI specification when another language or generated client fits your stack better than the official Node.js SDK.

FAQ

Common questions.

Does PostSider have a social media API SDK?
Yes. PostSider provides an official TypeScript and Node.js SDK that wraps the public API with typed application code.
Why use an SDK instead of raw REST?
An SDK is useful when you want autocomplete, typed request shapes and library-native helpers. Raw REST is still a good fit for simple scripts or languages where you prefer direct HTTP.
Can I generate a client for another language?
PostSider also provides an OpenAPI specification, which can be used with compatible tooling to generate clients for other languages and frameworks.
Does the SDK use the same publishing system as the dashboard?
Yes. The SDK works through the same PostSider publishing layer and connected-channel model as the REST API and web application.

Use the same publishing system from code

Connect the channels once. Keep the workflow in your stack.

Call REST directly, use the typed SDK, or expose the same publishing actions to an MCP-compatible agent.