List Discord guild roles
Returns all roles in a Discord guild. Useful for building role-mention pickers, role-permission UIs, or finding the role ID before calling the role-assign endpoint.
Roles are returned unordered — sort client-side by position if you
need Discord's UI ordering.
Caller must pass accountId of a Discord SocialAccount bound to this
guild (route verifies team access + guild match).
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Discord guild snowflake ID
Query Parameters
SocialAccount _id of the Discord account bound to this guild
Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.discord.listDiscordGuildRoles({ path: { guildId: 'guild_abc123', }, query: { accountId: 'account_abc123', },});console.log(data);{
"data": [
{
"id": "string",
"name": "string",
"color": 0,
"position": 0,
"permissions": "string",
"managed": true,
"mentionable": true,
"hoist": true
}
]
}{
"error": "Unauthorized"
}Delete a Discord channel message DELETE
Deletes a message from a channel, for moderation and cleanup. This cannot be undone. Deleting a message the bot did not send requires the bot to hold the Manage Messages permission, which the Zernio bot requests at install time. Deleting the bot's own message needs no extra permission. Ownership is verified by resolving the channel's guild and confirming the caller owns a Discord account bound to it.
Create a Discord guild role POST
Creates a new role in the guild. Requires the bot to hold the Manage Roles permission. Guilds that added the Zernio bot before role management shipped must re-invite it, because Discord applies the permission set at invite time. Discord's role hierarchy applies: the bot cannot create a role positioned at or above its own highest role, and cannot grant permissions it does not itself hold. Either attempt returns a 403 carrying Discord's own error.