Create an organization API key in Settings > API and call /public/v1 from your backend. Send the raw key in Authorization without Bearer. Current named keys support granular scopes. New keys default to read-only; grant posts:write only for integrations that must create or schedule posts. That scope can also publish, and older keys may retain broad grants. Keep secrets server-side.
For product developers
Social media scheduling API for apps and automations.
Use one REST API for connected social channels, drafts, scheduling and readback. Keep your business logic in your app, check each publishing result and use the calendar when a person needs to review the work.
- Shape REST under /public/v1
- Writes draft, schedule or now
- Plans API on every tier
The problem
Why a second dashboard never fits
- Every network means another OAuth dance, another token store and another failure mode.
- A timeout leaves you unsure whether the post exists, so support inherits the doubt.
- Per-channel pricing from API vendors punishes products that grow with their users.
- Platform tokens expire quietly and the first symptom is a failed customer launch.
What fits
The endpoints your product needs
Send a key with a create call and a retry returns the original post instead of a duplicate. Keep the key stable across retries.
A post that targets three networks reports three results. A failed target keeps its own error while the others publish.
Publish events are signed with HMAC-SHA256 and retried on failure, so downstream steps do not need to poll for outcomes.
Authenticate and get real channel IDs
# Read connected channel IDs first (raw key, no Bearer prefix)
curl --fail-with-body -H "Authorization: $POSTSIDER_API_KEY" \
https://api.postsider.com/public/v1/integrations
# Next: /developers/#rest-api has a complete draft-and-readback example.Start with a safe request
Get your first draft into PostSider.
A working API integration begins with a real channel ID, not a mock response. Read your channels, create one draft, then fetch it by the returned post ID before moving on to scheduling or publishing.
- 01Generate an API key
In Settings → API, create a named key with channels:read, posts:read and posts:write for this draft demo, then store it on your backend. New keys default to read-only, so opt in to posts:write deliberately. The API accepts the raw key in Authorization, without Bearer.
- 02Read connected channels
Call
GET /public/v1/integrations. Choose the actual returned ID and check the platform-specific publishing rules. - 03Save and verify one draft
Send
type=draftand read the resulting post by its returned ID. Only schedule after verifying the content, channel and status.
Need SDK code instead? See the Node.js and TypeScript guide or the SDK documentation. Named organization API keys support granular scopes in current PostSider builds. Existing legacy credentials may have broader grants. The posts:write scope allows drafting, scheduling and publishing; no separate draft-only scope is enforced. Keep keys server-side and require deliberate confirmation before write operations.
Using Claude, Codex or Cursor rather than REST? Follow our social media MCP server guide for OAuth, stdio and draft verification. This page focuses on developer REST/SDK integrations. For architecture and buyer-fit checks, use the five-point API evaluation below.
Compare social media scheduling APIs
Five questions to ask before choosing a publishing API.
An endpoint list is not enough. Evaluate how a provider handles your first failed request, the wrong destination, a required review and the difference between scheduled and published. Here is what the PostSider API actually provides.
- 01
Authentication and tenant separation
Where do your credentials live, and how do you stop one client workflow touching another?
PostSider REST uses a raw Authorization organization key from your backend. Current named keys allow scoped access (new keys default read-only), but posts:write can also publish and older keys may be broad. Each separately billed client organization needs its own credential and channels.
- 02
Create and retry behavior
If an HTTP request times out, can you retry without creating another post?
POST /public/v1/posts accepts an Idempotency-Key. Persist the exact JSON and key; retry with both unchanged. Changed payloads and in-flight requests must be handled as separate cases.
- 03
Proof of outcome
Can your application distinguish an accepted request from a scheduled post and a delivered post?
Save the returned post ID, fetch that exact record and check the channel-specific state. QUEUE is scheduled work, not evidence a network published it. Signed webhooks can notify you of later outcomes.
- 04
Review and approval
Is approval enforced in the product, or does an agent merely promise to ask first?
Standard supports draft-first manual review. Team, Pro and Ultimate include formal approval workflows. A write-capable API key or prompt is not, by itself, an approval boundary.
- 05
What you still build
Which business logic and platform restrictions remain your responsibility?
Your app supplies the content, chooses authorized channels and checks provider-specific media/settings requirements. PostSider does not offer a DM inbox, content generator or white-label reseller portal.
Choose the integration surface
One publishing layer. Different ways to call it.
REST is for deterministic apps, MCP is for compatible agent clients, and n8n/Make can use ordinary HTTP requests. All current paid tiers include MCP, API and SDK access.
n8n workflows Standard HTTP nodes with a downloadable manual-only draft example. Open guide → Make scenarios HTTP modules, raw API-key header, stable retries and readback. Open guide → AI agents over MCP Hosted OAuth or local stdio, read-only checks, confirmation and exact draft readback. Open guide →
These are documented product capabilities and evaluation criteria, not results of a performance benchmark against another vendor. For implementation details, consult the step-by-step scheduling tutorial and current API reference.
Plan fit
API access without a sales call
Standard
$20 / month
Five connected channels, one seat and API access on Standard. Compare the limits before building a multi-tenant product, and keep each organization credential isolated.
Straight answers
Where the API stops
- No white-label layer. Customers see PostSider calendars if you expose them.
- The API publishes. It does not read DMs, comments or mentions for you.
- Caption suggestions come from the post checker, not from a text generator.
Keep reading
Integration reading list
Developers How to schedule social media posts with an API Use a real social media scheduling API: connected channel IDs, UTC dates, idempotent writes and post readback. Includes n8n, Make and MCP paths. Developers Stop Double-Posting: Idempotency for Social APIs Retries are how posting scripts double-post. A publishing idempotency recipe: stable keys, check-before-create, webhook confirmation, with runnable snippets. Developers Webhooks: How to Know a Post Actually Went Live How PostSider's publish webhook actually works: the real payload shape, the retry behavior, the SSRF protection, and three things worth building on top of it.
FAQ
Questions from integration teams
What are the rate limits?
Sixty requests per minute per organization, shared by REST, MCP and the SDK because they hit the same API. Bursts are rejected with a clear status rather than silently dropped.
How do I handle expiring platform tokens?
Each connected channel keeps its own credentials and reports a reconnect state when a platform revokes access. Listen for that state, then send the account owner back through the platform OAuth flow before the next scheduled post.
Can I embed this inside a CMS or a SaaS product?
Yes. Make requests from your backend, never the browser. Current named organization keys support granular scopes, but posts:write also permits scheduling and publishing, and legacy keys can be broader. Use a separate PostSider organization and credential for each isolated tenant, grant only needed scopes and review plan limits.
What if a provider rejects my app or my customer account?
That happens on networks with an app review process. The post record keeps the provider error text, so the product can show a real reason instead of a generic failure, and the rest of the channels continue.
Where can I find the current API reference?
The published API documentation is at docs.postsider.com/api. Use the endpoint reference and your current instance to confirm available operations. For JavaScript and TypeScript, @postsider/node supports publishing and common channel operations.
Next
Pick the next closest fit
All nine client profiles The hub lists every workflow with its plan fit. Growth and marketing ops Campaign signals in, scheduled posts out, with evidence for every step. AI agent builders Connect AI agents through hosted OAuth or local MCP and verify every draft in the dashboard.
Product developers is profile set number 2 of 9 in the workflow guide.
Let your AI post
to social media for you.
Connect your accounts, add PostSider to your AI and publish your first post in a few minutes.
7-day free trial · 30+ networks · No credit card
