Load your API key
Keep the PostSider key in an environment variable and use it from a server process, worker or script. Do not ship it to browser code.
Node.js social publishing
Use normal server-side JavaScript to read your connected channels and publish through PostSider. Start with raw fetch, then move to the SDK if you want typed helpers.
Start with the social media scheduler API or browse the full developer platform.
How it works
There is no browser automation and no separate OAuth implementation in your Node service. Social accounts stay connected in PostSider; your code talks to one API.
Keep the PostSider key in an environment variable and use it from a server process, worker or script. Do not ship it to browser code.
Read the integrations endpoint first so your code knows the PostSider channel ID it should target.
Send the content, destination and publish mode to the public API. Use a future UTC timestamp when the post should be scheduled.
Keep the returned post ID and inspect publishing state later, or add webhooks when your backend needs event-driven updates.
Concrete example
This is a useful first request because every later post needs a target integration ID. The Authorization header takes the PostSider API key directly.
const apiKey = process.env.POSTSIDER_API_KEY;
if (!apiKey) throw new Error('POSTSIDER_API_KEY is not set');
const response = await fetch(
'https://api.postsider.com/public/v1/integrations',
{ headers: { Authorization: apiKey } }
);
if (!response.ok) {
throw new Error(`PostSider API returned ${response.status}`);
}
const channels = await response.json();
console.log(channels); Related developer guides
FAQ