OmniPosts documentation: posting, channels, queue and API

OmniPosts publishes one post to every channel you have connected, then tells you plainly, channel by channel, what happened.

Updated 22 October 2026

Start from what you're here to do.

OmniPosts is a social publishing tool for creators and for developers. You write a post once, choose the channels it goes to, and send it now, at a time you pick, or at the next free time in your weekly queue. Then OmniPosts shows you the result for each channel: posted, with a link; failed, with the reason and one thing to do about it; or still being checked.

What OmniPosts does

• One composer. Write once. Each channel shows a preview with its own character limit, and you can change the text for one channel without touching the others.
• A calendar and a queue. Post now, pick a time, or add the post to a weekly list of posting times. See Calendar and queue.
• Every post exactly once. If a platform does not answer clearly, OmniPosts checks whether the post went out before it does anything else. It never sends a post twice just to be safe. See Posts and results.
• Honest numbers. Engagement numbers appear only where a platform shares them. Where it does not, you see "Not available" and the reason, never a made-up zero. See Honest numbers.
• An API. Everything in the app is available over HTTP with API keys and signed webhooks.

About these docs

The pages are written in Markdown and kept in the repository next to the code, so they change with the product. If something here does not match what you see in OmniPosts, the product is right: tell us at join@omniposts.dev and we will fix the page.