One social media API
for all 13 platforms

No. You connect each social account once in OmniSocials with the platform's own sign-in (Telegram: press Start in the OmniSocials bot; Discord: Continue with Discord, or paste a webhook URL). After that, every API key of the workspace can post to it.

Create an API key in Settings, API and send it as a Bearer token in the Authorization header to https://api.omnisocials.com/v1. Keys start with omsk_live_ and belong to one workspace. The inbox needs the inbox:read and inbox:write scopes on the key, analytics the analytics:read scope. Requests and answers are JSON over HTTPS.

100 requests per minute per API key, on a rolling window. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Over the limit, the API answers 429 with a Retry-After header. Inbox replies have their own cap of 1,000 per workspace per 24 hours.

Up to 100 MB as a direct upload, and up to 1 GB from a URL or a presigned upload. POST /media/check tests a file against every platform you plan to post to before you create the post.

Five post events: post.scheduled, post.published, post.failed, post.approved and post.rejected. Each delivery is signed with HMAC-SHA256 in the X-OmniSocials-Signature header, so you can check it came from OmniSocials before you read it.

No, there are no test keys. Leave out schedule_at (scheduled_at in the SDKs) and a post stays a draft, so you can build against a real workspace without publishing. Many teams also keep a separate workspace with test accounts.

Yes. Coding agents such as Claude Code, Codex and Cursor use the CLI: npx skills add OmniSocials/omnisocials-agent-skills installs it as an agent skill, and it runs with your API key. Chat apps such as Claude and ChatGPT connect to the MCP server at https://mcp.omnisocials.com instead, with 56 tools.

Not yet. Today accounts connect in the OmniSocials app, one workspace per brand, which fits teams that automate their own or their clients' workspaces.

Platform integration, where your users connect their accounts inside your product, is coming soon.

Yes. The REST API, the SDKs, the CLI and the MCP server come with every seat: $10 per seat per month billed annually, or $12 billed monthly. Each workspace, teammate or client is a seat. The API also works during the 14-day trial; a card is needed to start it, and the first charge happens when the trial ends.

A workspace is a self-contained space for one brand or client. It has its own connected social accounts, calendar, team members and API keys. Most people start with one and add more as they take on clients.

Instagram, Facebook, LinkedIn (Profile and Page), YouTube, TikTok, X, Pinterest, Threads, Bluesky, Mastodon, Google Business, Telegram and Discord, all through the same API, the app and one calendar.

Yes. Create as many workspaces as you need, each with its own accounts and team. Every workspace is a seat at $10 per month billed annually.

Invite teammates to a workspace and assign roles. Permissions control who can draft, schedule, approve and publish, so everyone has the right level of access.

You can try OmniSocials free for 14 days before you pay. If something is not right after that, reach out to support and we will help.

Approval workflows let agents, your code and team members draft posts that route to a reviewer. Nothing publishes until someone signs off, and post.approved or post.rejected tells your code what was decided.