Social Media Scheduling API
for Developers

Schedule content across every major platform with a single API call. Set a time, pick a timezone, and Onepostly delivers your posts at the exact moment.

Start for free

No credit card required

import { Configuration, PostsApi } from "@onepostly/sdk"; const posts = new PostsApi( new Configuration({ apiKey: process.env.ONEPOSTLY_API_KEY }), ); await posts.createPost({ createPostBody: { text: "Ship once. Post everywhere.", scheduledFor: "2027-06-01T09:00:00", timezone: "America/New_York", destinations: [{ accountId: "conn_x_123" }, { accountId: "conn_ig_456" }], }, });

Trusted by developers and teams shipping across every platform

The boring parts, handled

Every platform behind one integration

One integration covers publishing, scheduling, and analytics. Platform changes, app reviews, token refreshes, and rate limits are ours to absorb.

Features

Schedule, publish, and measure.

Changelog: faster media uploads

PublishedMon, 5 Oct09:30

Meet the new analytics view

PublishedTue, 6 Oct17:15

Planning your calendar, the short version

Thu, 8 Oct10:45Europe/Istanbul

We are at the API meetup today

Fri, 9 Oct13:00America/New_York

Case study: shipping every day

Mon, 12 Oct08:30Europe/London

Live demo: retries and webhooks

Tue, 13 Oct19:00Asia/Tokyo

Uptime report for last month

Wed, 14 Oct11:20America/Los_Angeles

Post Scheduling

Pick the time and timezone. Nothing goes out until its scheduled moment, and you can cancel any time before.

ReelsText
Video
Photos
Story

Images, Videos & Carousels

Upload images, videos, carousels, Stories, and Reels. One payload, every destination.

Webhooks & Events

Publish, fail, comment, or DM. Every event hits your endpoint the moment it happens.

First Comment Support

Add a first comment to the same call. It publishes alongside the post where supported.

Normalized Analytics

One call returns likes, comments, and shares from every platform in the same shape.

Why Onepostly?

You call one API, we handle the rest.

Onepostly API

  • App reviews and OAuth handled

    Platform apps and token refresh handled for you

  • One API key

    Connect once and publish everywhere with one key

  • One shape for every surface

    Comments DMs and metrics in normalized JSON

  • Platform changes absorbed

    Endpoint contracts stay stable when APIs shift

Building it yourself (platform APIs)

  • A separate app per platform

    App reviews and OAuth verification take months

  • A token refresh flow per platform

    Rate limits and expiry tracking on your side

  • A different shape per platform

    Inconsistent schemas across social networks

  • Every breaking change on you

    API version bumps and deprecations to track

Beyond publishing

Comments, DMs, and metrics on the same API.

Same accounts, same API key. Conversations, moderation, automations, and numbers run through the integration you already have.

Inbox API

Conversations from every platform, one inbox

All platformsAll accounts
mira.buildsCan you send the setup guide?2m
kai.drawsLoved the launch post!14m
james.codesIs there a Python SDK?1h
Engagement API

Like, bookmark, and repost as API calls

MBmira.builds2h

Launch day is live. Everything shipped from one call.

128248
Automations API

Comment to DM automations

MB@mira.buildsGUIDE please
KD@kai.drawssend the GUIDE
MBmira.buildsHi! Sent the guide · now
KDkai.drawsHi! Sent the guide · 1m
Analytics API

Metrics from every platform, one shape

PlatformLikesCommentsShares
Instagram1,2848641
TikTok3,410214132
LinkedIn4863218
X7924563

Frequently asked questions

Common questions about scheduling posts through the Onepostly API, timezones, media, and managing scheduled jobs.

Schedule up to one year ahead. Pass a timezone-naive local datetime in scheduledFor and an IANA timezone such as America/New_York or Europe/Berlin.

Yes. Include multiple destinations in one POST /v1/posts request. Each connection gets the same schedule and Onepostly delivers when the local time arrives.

Any valid IANA timezone. If timezone is omitted, Onepostly defaults to UTC. Do not send Z or a numeric offset on scheduledFor.

Yes. DELETE /v1/posts/:id cancels scheduled, queued, or processing posts before they publish. It does not remote-delete content that already went live.

The post still fires on schedule, and each destination reports its own outcome, so you can show which went out. A failure carries a reason and stays failed — waiting does not change it.

Yes. Schedule text, images, videos, and multi-image posts. Media rules are validated per destination when you create the job.

Yes. The OAuth screens your users see carry neutral names like Social Media Connector rather than our brand, so the experience reads as fully yours.