Create scheduled event with the Discord API

Creates an event in a server and returns it with its id. An event outside Discord takes entity_type 3 with entity_metadata.location and scheduled_end_time; an event in a voice or stage channel takes entity_type 2 or 1 with channel_id. The bot needs Create Events, and a server holds up to 100 scheduled or active events.

Identifier
discord_create_scheduled_event

The request

POST https://connect.reportei.com/api/tools/discord_create_scheduled_event/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "guild_id": "<guild_id>",
    "name": "<name>",
    "privacy_level": 2,
    "scheduled_start_time": "<scheduled_start_time>",
    "entity_type": 1
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
guild_idstringYesId of the server, from List guilds.
namestringYesName of the event, up to 100 characters.
descriptionstringNoDescription of the event, up to 1000 characters.
privacy_levelintegerYesAlways 2: the event is visible to the members of the server.Values: 2
scheduled_start_timestringYesStart of the event, ISO 8601 with offset, for example 2026-11-05T19:00:00-03:00.
scheduled_end_timestringNoEnd of the event, ISO 8601 with offset. Required when entity_type is 3.
entity_typeintegerYesWhere it happens: 1 in a stage channel, 2 in a voice channel or 3 outside Discord.Values: 1, 2, 3
channel_idstringNoId of the voice or stage channel, from List channels. Required for entity_type 1 and 2, left out for 3.
entity_metadataobjectNoRequired for entity_type 3.

Supported connections

Your customer connects their Discord account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/discord_create_scheduled_event. It becomes your agent's tool definition with no conversion.

Other Discord tools

See all 12 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.