One agent for the whole social stack
› claude
Claude Code
MCP client
~/software
Publish, schedule, and measure on X through one endpoint.
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: "Hello from Onepostly",
mediaKind: "text",
destinations: [{ accountId: "YOUR_X_ACCOUNT_ID" }],
},
});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": "Hello from Onepostly",
"mediaKind": "text",
"destinations": [{"accountId": "YOUR_X_ACCOUNT_ID"}],
}
)curl -X POST https://api.onepostly.com/v1/posts \ -H "x-api-key: op_YOUR_KEY" \ -H "Content-Type: application/json" \ -d '{ "text": "Hello from Onepostly", "mediaKind": "text", "destinations": [ { "accountId": "YOUR_X_ACCOUNT_ID" } ] }'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.
Wallet billing, weighted character limits and the paid-tier long-post ceiling, threads, scheduling, and what X does not expose through the API.
X charges per call, so X activity draws from a prepaid wallet at X's own prices, nothing added. Top up in Dashboard → Settings → Billing; an empty wallet returns 402 INSUFFICIENT_WALLET.
X counts weighted units, not characters: emoji and non-Latin scripts count double, and a link always counts as 23. The limit follows the account — 280, or 25,000 with a paid X subscription.
Yes. Send the root post plus the follow-ups in threadItems and each publishes as a reply to the one before it, up to 25 replies with their own media.
Yes. Pass scheduledFor with an IANA timezone and the post goes out when that moment arrives; cancel any time before then with a single delete call. Remote delete removes a published thread as a whole.
Stories, polls, editing a published post, reply settings, and direct messages. Media posts can still carry a geoRestriction allowlist of up to 25 countries.
Call GET /v1/analytics for normalized metrics. The shares field covers retweets plus quotes, and the shape matches every other platform.
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.