# OmniPosts

> OmniPosts (jamp.sh) is a social media scheduling tool and HTTP API that posts to Bluesky, Mastodon and Telegram, then reports per channel whether each post went out. Made by Moodsboard Technologies Private Limited, India.

Write a post once, publish or schedule it to every connected channel, and read an honest
result per channel: posted, failed with a reason, or still being checked. Never a made-up
number where a platform shares none.

Name and address: OmniPosts (one word) lives at jamp.sh. Other products with a
similar name are not this one. Data: channel credentials are encrypted, you can export
or delete everything yourself, and your content is not sold or used to train AI models.

## Product

- [Product](https://jamp.sh/product): what OmniPosts does, screen by screen.
- [Channels](https://jamp.sh/channels): every channel and its status, Available or
  Coming soon (live). Available: Bluesky, Mastodon and Telegram. Coming soon: Facebook Pages, Instagram, LinkedIn, LinkedIn Pages, Threads, TikTok, TikTok for Business, X, YouTube.
- [Pricing](https://jamp.sh/pricing): plan limits; Free is open, Creator and Pro are in beta with a waitlist.

## Docs

- [Quickstart](https://jamp.sh/docs/quickstart): account, first channel, first post,
  in the app or with the API.
- [Posts and results](https://jamp.sh/docs/concepts/posts-and-results): one post, one
  result per channel, and why OmniPosts checks instead of resending.
- [Honest numbers](https://jamp.sh/docs/concepts/honest-numbers): engagement numbers
  only where a platform shares them; otherwise Not available, with the reason.
- [Workspaces and members](https://jamp.sh/docs/concepts/workspaces): a workspace holds
  channels, posts, media, API keys and the plan; invite people with a link, each with
  a role, and switch between the workspaces you belong to.
- [Connect an agent](https://jamp.sh/docs/agents/connect): add OmniPosts to Claude
  Code, Cursor or another MCP client with a scoped API key.
- [API reference](https://jamp.sh/docs/api): base URL, auth, errors and every resource.
- [Idempotency](https://jamp.sh/docs/api/idempotency): an Idempotency-Key so a retry
  never posts the same thing twice.
- [Webhooks](https://jamp.sh/docs/api/webhooks): signed calls (Standard Webhooks) when
  a post publishes or fails.
- [All docs in one file](https://jamp.sh/llms-full.txt): every docs page as Markdown.

## Trust

- [Security](https://jamp.sh/security): how accounts, tokens and data are protected.
- [Privacy](https://jamp.sh/privacy): what is collected, why, and how to delete it.
- [DPA](https://jamp.sh/dpa): the data processing agreement.

## For agents and developers

- The API contract (OpenAPI 3.0): https://jamp.sh/openapi.yaml (also as JSON: https://jamp.sh/openapi.json)
- MCP server (streamable HTTP, stateless): POST https://jamp.sh/mcp
  Tools: list_providers, list_channels, validate_post, create_post, list_posts,
  get_post, cancel_post, retry_post, upload_media_from_url, start_channel_connect,
  get_connect_session, get_post_metrics.
  How to connect a client: https://jamp.sh/docs/api/mcp

Auth, API and MCP alike: `Authorization: Bearer <api-key>`. A person creates keys at
https://jamp.sh/app/settings/agents (Settings → Agents & API) or POST /v1/api-keys with a session; a key
can be limited to scopes (posts:write, media:write, …) and can expire. A key belongs
to one workspace and sees only that workspace's channels and posts. A channel that
reads Coming soon cannot be connected yet; /v1/providers says which are available.
Errors: `{error: {code, message, details?}}`; 429 always carries `Retry-After`.
A post is a group with one target per channel; a target's status is final only at
published, failed or cancelled. Never re-send a post whose outcome is unknown.

## Optional

- [About](https://jamp.sh/about): who runs OmniPosts and how it works.
- [Developers](https://jamp.sh/developers): the API and MCP server at a glance.
- [Changelog](https://jamp.sh/changelog): what shipped, newest first (feed: https://jamp.sh/changelog.atom).
- [Support](https://jamp.sh/support): where answers are, and who to write to.
- [Contact](https://jamp.sh/contact): email and company details.