One agent for the whole social stack
› claude
Claude Code
MCP client
~/software
Publish, schedule, and measure on Threads 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_THREADS_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_THREADS_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_THREADS_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.
Caption limits, reply chains, quotes, daily limits, and what Threads does not offer.
Threads caps everything at 500 characters — posts, captions, and every thread segment. Cross-posting from a longer-limit network fails here, so send a shorter Threads-specific text.
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. firstComment adds one reply under the root.
Yes. Alongside text, image, video, and carousel posts, a Threads post can quote another Threads post.
Threads allows roughly 250 API-published posts per rolling 24 hours, and every item in a chain counts toward that total.
None of them. Threads exposes reposts and replies only — there is no like or bookmark API, no Stories, and no messaging. Repost and unrepost are both available.
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.