Skip to content

TypeScript + PostSider SDK

Schedule social media posts with TypeScript

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

Keep the social integration typed and server-side.

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.

01

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.

02

Create the client once

Initialize it with a server-side API key and reuse the client from the service or worker that owns your publishing workflow.

03

Read integrations before posting

Load connected channels and select the destination by ID instead of hard-coding provider credentials into your application.

04

Use types around failures too

Treat API errors, disabled channels and publishing state as explicit application states instead of assuming every scheduled post succeeds.

Concrete example

Find a connected LinkedIn channel with the SDK

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');

FAQ

Common questions.

Can I schedule social media posts from TypeScript?
Yes. TypeScript backends can use the PostSider SDK or call the REST API directly to create publishing actions for connected channels.
Does the SDK provide TypeScript types?
Yes. The official client is intended for typed TypeScript and Node.js application code around the PostSider public API.
Can I use it in serverless functions or workers?
Yes. Use the SDK anywhere you can keep the PostSider credential server-side, including backend frameworks, workers and serverless functions.
Is the SDK a different API?
No. It is a typed client around the same public publishing API, so you can mix SDK calls with direct REST requests when needed.

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.