List Discord scheduled events
Return all scheduled events in the guild. Events are distinct from messages — they appear in the server's Events panel and Discord auto-notifies interested members ahead of start time.
Pass withUserCount=true to include user_count (number of members
who RSVP'd) on each event. Useful for surfacing engagement.
API key authentication - use your Zernio API key as a Bearer token
In: header
Path Parameters
Query Parameters
Include user_count on each event.
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.listDiscordScheduledEvents({ path: { guildId: 'guild_abc123', }, query: { accountId: 'account_abc123', },});console.log(data);{
"data": [
{
"id": "string",
"guild_id": "string",
"channel_id": "string",
"creator_id": "string",
"name": "string",
"description": "string",
"scheduled_start_time": "2019-08-24T14:15:22Z",
"scheduled_end_time": "2019-08-24T14:15:22Z",
"privacy_level": 2,
"status": 1,
"entity_type": 1,
"entity_id": "string",
"entity_metadata": {
"location": "string"
},
"user_count": 0,
"image": "string"
}
]
}{
"error": "Unauthorized"
}List pinned messages in a Discord channel GET
Returns the channel's pinned messages, sorted most-recently-pinned first. Discord caps a channel at 50 pinned messages and returns the full list unpaginated. Bot needs READ_MESSAGE_HISTORY in the channel (granted by default BOT_PERMISSIONS).
Create a Discord scheduled event POST
Create a guild scheduled event. Three event types, selected via the discriminator on `entity.type`: - `external` — off-platform (Zoom, in-person, livestream). Requires both `location` and `endsAt`. Most common type for scheduler integrations. - `voice` — hosted in a Discord voice channel. Requires `channelId`. - `stage` — hosted in a Discord stage channel. Requires `channelId`. Bot needs MANAGE_EVENTS in the guild. Existing installs (pre-events PR) need a re-invite OR a server admin manually granting the permission — see route header for details.