Dovkie
Sign in
Back to monitors

discord

Discord API

REST
OpenAPI (JSON)
https://raw.githubusercontent.com/discord/discord-api-spec/main/specs/openapi.json
Additive AI classification

Add optional liveliness field to invite object

The invite object schema now includes an optional liveliness field that returns a new GuildLivelinessResponse object containing guild message activity data. This is a purely additive change that does not affect existing integrations.

Alert history

  • Additive

    Add optional liveliness field to invite object

    The invite object schema now includes an optional liveliness field that returns a new GuildLivelinessResponse object containing guild message activity data. This is a purely additive change that does not affect existing integrations.

  • Informational

    Add int32 format annotation to integer fields

    Added "format": "int32" annotation to four integer fields with maximum: 21600 constraint across the Discord API specification. This is a documentation enhancement that clarifies the type representation in the OpenAPI schema without changing runtime behavior or field semantics.

  • Additive

    Add target_channel_id and target_message_id to invite API

    Added two new optional query parameters (target_channel_id and target_message_id) to invite-related endpoints, and corresponding response fields to the invite schema. These are purely additive fields that do not affect existing integrations.

  • Additive

    Add optional is_spoiler field to audit log entries

    A new optional is_spoiler field (boolean or null) has been added to the audit log entry schema. This is a backwards-compatible addition that allows clients to optionally read spoiler information from audit log changes.

  • Additive

    Add PRUNE_REQUIRES_ADMIN guild feature

    A new guild feature flag PRUNE_REQUIRES_ADMIN has been added to indicate when a guild has restricted member prune operations to administrators and the guild owner. This is an additive change that introduces a new enum constant without affecting existing functionality.

  • Additive

    Add role_ids field to message interaction callback

    A new optional role_ids field has been added to the CreateMessageInteractionCallbackRequest schema. It accepts a string, array of Snowflake IDs (up to 250 unique items), or null. This allows filtering message visibility by roles in interaction responses.

  • Informational

    Rename BasicApplicationResponse to BasicApplicationResponseWithBot

    The schema BasicApplicationResponse has been renamed to BasicApplicationResponseWithBot throughout the OpenAPI spec. This is a documentation/naming change that clarifies the schema's purpose and is reflected in the message response schemas that reference it, but does not alter the actual API behaviour or response structure for clients.

  • Breaking

    InviteChannelRecipientResponse now requires id and avatar fields

    The InviteChannelRecipientResponse schema adds two new required fields: id (SnowflakeType) and avatar (nullable string). While these are new response fields (additive in terms of data), marking them as required means any client-side schema validation or strict deserialization that previously only expected username will now fail if it enforces the required list — and any mock/stub implementations that don't return these fields will be considered non-compliant. Existing clients that simply read the response are unaffected, but strict validators will break.

  • Additive

    Add scheduled event recurrence and exceptions support

    The Discord API adds support for recurring guild scheduled events with new recurrence_rule fields, exception handling endpoints, and a new /guilds/{guild_id}/incident-actions endpoint. New schema types UserProfileRuleResponse, UserProfileUpsertRequest, UserProfileUpsertRequestPartial, GuildIncidentActionsRequest, GuildIncidentsDataResponse, GuildScheduledEventExceptionCreateRequest, RecurrenceRule, and RecurrenceRuleResponse are introduced. All existing endpoints and fields remain functional—this release is purely additive.

  • Additive

    Add optional provisional_user_id field to API response

    A new optional response field provisional_user_id (nullable or Snowflake ID) has been added to an API response object. This is additive and will not break existing clients that do not depend on this field.