One agent for the whole social stack
› claude
Claude Code
MCP client
~/software
Publish, reply, and measure across 9 platforms, all from one integration.
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.",
mediaUrls: ["https://cdn.example.com/launch.png"],
destinations: [{ accountId: "conn_x_123" }, { accountId: "conn_ig_456" }],
},
});import os
from onepostly import ApiClient, Configuration
from onepostly.api.posts_api import PostsApi
posts = PostsApi(ApiClient(
Configuration(access_token=os.environ["ONEPOSTLY_API_KEY"]),
))
await posts.create_post(create_post_body={
"text": "Ship once. Post everywhere.",
"mediaUrls": ["https://cdn.example.com/launch.png"],
"destinations": [{"accountId": "conn_x_123"}, {"accountId": "conn_ig_456"}],
})curl -X POST https://api.onepostly.com/v1/posts \ -H "x-api-key: op_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "text": "Ship once. Post everywhere.", "mediaKind": "image", "mediaUrls": ["https://cdn.example.com/launch.png"], "destinations": [ { "accountId": "conn_x_123" }, { "accountId": "conn_ig_456" } ] }'The boring parts, handled
One integration covers publishing, scheduling, and analytics. Platform changes, app reviews, token refreshes, and rate limits are ours to absorb.
Changelog: faster media uploads
Meet the new analytics view
Planning your calendar, the short version
We are at the API meetup today
Case study: shipping every day
Live demo: retries and webhooks
Uptime report for last month
Pick the time and timezone. Nothing goes out until its scheduled moment, and you can cancel any time before.
Upload images, videos, carousels, Stories, and Reels. One payload, every destination.
Publish, fail, comment, or DM. Every event hits your endpoint the moment it happens.
Add a first comment to the same call. It publishes alongside the post where supported.
One call returns likes, comments, and shares from every platform in the same shape.
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
Same accounts, same API key. Conversations, moderation, automations, and numbers run through the integration you already have.
Launch day is live. Everything shipped from one call.
Common questions from teams shipping on Onepostly.
Direct platform integrations take weeks of engineering each. With Onepostly you go from API key to first published post in minutes, using one request shape for every network.
No. Publishing runs on each platform's own official API, so a post sent from Onepostly is treated the same as one made in the platform's own app.
No. Platform apps, their approvals, the OAuth handshake, and token renewal are handled for you. You connect accounts in the dashboard, then call one API with your key.
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.
Yes. An MCP server ships with the product, so a client like Claude or Cursor can connect accounts, create and schedule posts, read analytics, and remove published content.
Start free with a connected account included, then pay a flat monthly rate per account that drops as you connect more. X usage bills from a prepaid wallet.