Calls posted in a Discord server can be traded automatically in two ways that Discord permits. A bot application can read the channel once someone with permission in that server adds it. Or the person who makes the calls can send each one straight to a program that places orders and post it to Discord through a webhook. Automating your own user account to read a server is forbidden, and it can cost you the account.
What does Discord allow?
Discord has an account type made for automation. Its support article on automated user accounts says "Discord's API provides a separate type of user account dedicated to automation, called a bot account." It goes on, "Bot accounts can be created through the applications page, and are authenticated using a token (rather than a username and password)."
A bot enters a server by being added to it. The OAuth2 docs say "Bots are added to guilds through the OAuth2 API, and cannot accept normal invites." Whoever opens the install link is "prompted to add the bot to a guild in which they have proper permissions." The decision belongs to the people who run the server.
Webhooks are the second permitted tool, and they work in the other direction. The webhook docs call them "a low-effort way to post messages to channels in Discord." A webhook writes into a channel and reads nothing from it.
Why are self-bots and user tokens banned?
A self-bot is a normal account driven by a script. The support article says automating normal user accounts "outside of the OAuth2/bot API is forbidden, and can result in an account termination if found."
The Community Guidelines repeat it as rule 14, "Do not use self-bots or user-bots. Each account must be associated with a human, not a bot." That page also states, "These Guidelines are incorporated into our Terms of Service". The Terms add their own ban on "scraping our services without our written consent, including by using any robot, spider, crawler, scraper, or other automatic device, process, or software".
A tool that asks you to paste your Discord token wants to read a server as you. Discord's Developer Policy closes that door from the developer's side. Its rule 4 reads "Under no circumstances may you or your Application request or attempt to obtain login credentials from Discord users. This includes information such as passwords or account access or login tokens."
So the tool is barred from asking, and you are barred from running the result. The quality of the calls changes none of it.
What if you run the server?
Then the permitted route is short. Create an application in the Developer Portal, add its bot to your server, and have it listen to the channel where calls are posted.
Reading message text takes one extra step. The gateway docs class MESSAGE_CONTENT as a privileged intent that "permits your app to receive message content data across the APIs." They add, "Before you can specify any of these privileged intents in your IDENTIFY payload, you must enable the specific privileged intents you need in the Developer Portal."
A small private bot needs no review, because "Apps with fewer than 10,000 users can access privileged intents by enabling them in the Developer Portal." One condition applies at any size, "You may only enable a privileged intent if your use case requires it to function and is consistent with our Developer Policy."
That policy also limits what a bot does with the messages it reads. Discord's Developer Terms define API Data as "any data, information, or other content you obtain through the APIs". Rule 15 of the policy says "Do not use API Data for any purpose outside of what is necessary to provide your stated functionality." Rule 18 says "Do not sell, license, or otherwise commercialize API Data or any of Discord's services". Rule 21 bars training AI models on message content obtained through the APIs unless Discord gives express permission. A bot whose stated function is placing orders from the calls should use the messages for that purpose.
A bot built for one server can stay closed to everyone else. Of the Public Bot setting, the OAuth2 docs say "If unchecked, only you can add the bot to guilds."
There is also a design that needs no reading at all. If the calls begin in your own tool, such as a script or a chart alert, send each one to the order program first and to Discord second. The webhook docs say "Incoming Webhooks can post messages to channels with a generated token", so the same event can post the call for members. The channel then displays what was traded, and no program depends on parsing it.
What if you are only a member?
A member without the needed permissions can't add a bot to someone else's server, and the member's own account can't be automated. Each remaining option runs through the owner.
The first is to ask the owner to install an app for the purpose. The Terms place that step with administrators, saying "third parties can build apps for content moderation or interactive games that server administrators can add to their servers on Discord". Their examples are moderation and games, and trading isn't mentioned.
The second is an announcement channel. Discord's Announcement Channel FAQ says these channels "include a Follow button, allowing server members to receive updates in their own servers." It adds that a published message "appears as a regular message in all following servers". The message reference gives such a post the IS_CROSSPOST flag, described as "this message originated from a message in another channel (via Channel Following)". A bot in your own server should receive it there as an ordinary message, under the same intent. The FAQ sets one limit, "Announcement Channels are only available to servers with Community enabled."
Discord's pages describe following as a feature and say nothing about trading on followed posts. The data rules above apply to a bot that reads them.
Keep what arrives for your own orders. The Terms bar "selling, licensing, or otherwise commercializing content or data obtained from our services", and the server may have rules of its own about reuse.
If the owner offers neither route, ask whether the alerts are delivered anywhere outside Discord. Failing that, the permitted answer is to place the trades by hand.
What does a call need before a program can trade it?
A call written for people is often ambiguous to a parser. "Looking at XYZ calls into the close" names no contract, no price and no size.
A program needs every call in one fixed format. For an option, that means the ticker, call or put, strike, expiration and a limit price on a single line. Exits need their own messages naming the same contract, since a reply that says "out" depends on context a parser doesn't have.
Format also decides whether the bot can see the call at all. In the gateway docs, "the content, embeds, attachments, components, and poll fields in message objects all contain message content and therefore require the intent." A call posted as a screenshot arrives as an attachment with no text to parse.
Decide in advance what an edited message means. A safe rule treats the first version as the call and flags any edit for a person to review.
Where should the orders go first?
Send them to a broker's paper account before a live one. On Alpaca's paper trading page, orders follow the live flow but are filled by a simulator from real-time quotes and never reach an exchange. That is enough to prove the parsing and the order fields.
Paper also exposes duplicates. tastytrade's idempotency guide warns that its API doesn't deduplicate retried order submissions. A call that reaches the program twice can become two positions unless the program remembers which message ids it has already handled.
Which methods stay inside the rules?
| Method | Does Discord's published text allow it? | Source |
|---|---|---|
| Bot application added by the server's admins | Yes, within the Developer Policy's data rules | OAuth2 docs, Developer Policy |
| Incoming webhook posting calls from your own tool | Yes | Webhook docs |
| Following an announcement channel into your own server | The feature is documented, and trading on followed posts isn't addressed | Announcement Channel FAQ, message reference |
| Script logged in as your user account | No | Community Guidelines, rule 14 |
| Tool that asks for your user token or password | No | Developer Policy, rule 4 |
| Scraper reading the server without Discord's consent | No | Terms of Service |
Discord's Platform Manipulation Policy Explainer also tells users not to modify the Discord client, and it names automating account actions. A patched client that forwards messages belongs with the No rows.
AI tools wrote this article. Its facts were checked against the official docs linked above.
Trading involves risk of loss.
Top comments (0)