The Discord API,without a bot

No. OmniSocials posts through the channel’s incoming webhook, so no bot joins your server, there is nothing to host and no token expires. In OmniSocials you open Channels, add Discord and press Continue with Discord, or paste a webhook URL. Your code calls the OmniSocials API with an API key.

In Discord, open Server Settings, then Integrations, then Webhooks. Press New Webhook, pick the channel and press Copy Webhook URL, then paste it in OmniSocials. With Continue with Discord you skip this: you pick the server and the channel on Discord’s own screen and Discord makes the webhook. You need the Manage Server permission in that server.

Yes. Add schedule_at to POST /v1/posts/create and OmniSocials sends the message at that time, or use POST /v1/posts/create-and-publish to send it now. A webhook on its own posts right away and has no schedule. OmniSocials’ own events, post.scheduled and post.published, tell your app when a post is planned and when it is out.

The webhook’s. Discord shows every message under the webhook’s name and picture, and a post from OmniSocials can’t set its own. Change them in Discord, in the webhook’s settings under Server Settings, Integrations, Webhooks. GET /v1/accounts returns the name as platform_details.webhook_name.

No. A sent post can’t be edited through OmniSocials; the API changes draft and scheduled posts only. You can take it down at any time: Delete from Discord on the post in OmniSocials removes the message, and the message with the video links if there is one. Only the webhook that sent a message can remove it, so after a reconnect with a new webhook, remove older posts in Discord yourself. DELETE /posts/{id} removes the post from OmniSocials only.

No. A webhook can only post to its one channel and read back the messages it sent itself. OmniSocials reads those for their reactions and poll votes, and never sees the server’s other channels, its members or anyone’s messages, which is also why Discord is not in the Social Inbox. Continue with Discord reads the server’s name and icon once, when you connect.

Posts to the channel stop, each with a message that says why, and GET /v1/accounts shows needs_reconnect: true with the reason “The webhook was deleted in Discord”. Resetting the webhook’s URL in Discord does the same. You get an email. Reconnect the channel in OmniSocials: Continue with Discord makes a new webhook, or paste the URL of a new one.

Yes, through the hosted MCP server. create_post, create_and_publish_post and update_post take the same discord options, get_post shows where the message landed and get_post_analytics returns the reaction total.

Yes. Discord charges nothing for its API, and a webhook needs no bot and no sign-in to post to its channel. What it leaves to you is everything around the post: a scheduler, file uploads, the poll and button fields, retries and reading reactions back. With OmniSocials, Discord is part of the plan, $10 per seat per month billed annually, and posting to it uses no credits.

One plan with every feature included: $10 per seat per month billed annually, or $12 billed monthly. Team members and client seats cost the same. Every account starts with a 14-day free trial.

The REST API, the SDKs, the CLI, webhooks and the MCP server are part of that one plan.