Install the PostSider client
Use the official TypeScript and Node.js package when this integration is part of a typed backend rather than a one-off HTTP script.
TypeScript + PostSider SDK
If your publishing workflow already lives in a TypeScript backend, use the PostSider client for typed access to the same channels and API used by the dashboard.
Start with the social media scheduler API or browse the full developer platform.
How it works
The SDK is useful when social publishing is part of a real application codebase: channel lookup, scheduling and failure handling can live beside the rest of your domain logic.
Use the official TypeScript and Node.js package when this integration is part of a typed backend rather than a one-off HTTP script.
Initialize it with a server-side API key and reuse the client from the service or worker that owns your publishing workflow.
Load connected channels and select the destination by ID instead of hard-coding provider credentials into your application.
Treat API errors, disabled channels and publishing state as explicit application states instead of assuming every scheduled post succeeds.
Concrete example
The exact post payload depends on the network and publishing mode. Start by resolving an enabled channel, then use the current SDK/API schema for the publishing call.
import Postsider from '@postsider/node';
const postsider = new Postsider(
process.env.POSTSIDER_API_KEY!
);
const channels = await postsider.integrations();
const linkedin = channels.find(
(channel) => channel.identifier === 'linkedin' && !channel.disabled
);
if (!linkedin) throw new Error('No enabled LinkedIn channel'); Related developer guides
FAQ