Omniplex Docs

Listing a Bot

How to submit a Discord bot to Omniplex and manage it afterward.

Bots are submitted through the API, there's no Discord command for this, unlike managing a server listing (see Infernoplex).

You'll need to authenticate first. See Authentication for how to get a user or bot token.

Before you submit

A few things have to be true before PUT /bots will accept your bot:

  • The bot must already be in Discord and public. Omniplex looks the bot up by ID and rejects the submission if it isn't a real, public bot.
  • It can't already be listed. Submitting the same bot ID twice returns a conflict.
  • Submissions are rate limited to 5 per minute.

What you send

PUT /bots
FieldRequirement
bot_idNumeric Discord user ID
client_idNumeric Discord application ID
short30–150 characters
longAt least 500 characters
prefix1–10 characters
inviteHTTPS URL
library1–50 characters
extra_linksRequired, may be empty
tags1–5 unique tags, each 3–30 characters
nsfwBoolean
staff_noteOptional, up to 512 characters
team_ownerOptional, see below

Your server count and avatar are read directly from Discord, not sent by you.

Ownership

If you don't send team_owner, Omniplex creates a brand-new team for you automatically and makes you its owner. If you do send one, you need the add_bots permission on that team, see Teams & Permissions for how team permissions work.

After submission

New listings go through moderation before appearing publicly. Content is also run through an automated check as a reviewer signal, this never blocks submission, it just flags things for a human to look at.

Managing your bot afterward

  • Update settings: PATCH /bots/{id}/settings (short/long description, prefix, invite, library, links, tags, NSFW flag, and whether the bot opts out of the CAPTCHA on its vote page). Requires edit_bots.
  • Sync slash commands: PUT /bots/{id}/commands keeps the command list shown on your listing up to date.
  • Post changelogs: POST /bots/{id}/changelogs publishes a changelog entry to your listing's page.
  • Delete the listing: DELETE /bots/{id}, requires delete_bots.

Any of these can be called with a user token, a team token, or, for settings, the bot's own token.

On this page