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 fields for lobby and author support to messages

New optional fields and schemas have been added to Discord's message and user models: additional_name (nullable string, 1-80 chars) on user and group DM channel objects; lobby_member field (referencing new MessageLobbyMemberResponse schema) on message objects; and additional_name on the new MessageLobbyMemberResponse schema. These are all additive changes with no impact on existing integrations.

Alert history

  • Additive

    Add optional fields for lobby and author support to messages

    New optional fields and schemas have been added to Discord's message and user models: additional_name (nullable string, 1-80 chars) on user and group DM channel objects; lobby_member field (referencing new MessageLobbyMemberResponse schema) on message objects; and additional_name on the new MessageLobbyMemberResponse schema. These are all additive changes with no impact on existing integrations.

  • Breaking

    ApplicationResponse adds required field eligible_oauth2_scopes

    A new field eligible_oauth2_scopes (array of OAuth2Scopes) has been added to the ApplicationResponse schema and placed in the required array. Because it is marked required, clients that validate response payloads against this schema (e.g. strict deserializers or generated SDK models) may break if they receive older responses lacking this field, or if server responses that now include it are not handled. Clients writing back this schema shape also need to be aware of the new required field.

  • Breaking

    minLength: 1 added to a string field (max 1024) in Discord API spec

    A "minLength": 1 constraint was added to a string field that previously had only a maxLength of 1024. This means empty strings ("") are no longer valid for this field — clients sending empty strings will receive a validation error. The exact endpoint and field path are not shown in the diff context, but this is a tightening of an existing constraint.

  • Additive

    Add restriction_count to rate limit response

    A new optional field restriction_count (integer, int32 format) has been added to the rate limit response object. This is a purely additive change that does not affect existing clients.

  • Breaking

    minLength: 1 added to external_auth_token and external_user_id fields

    Three request fields now have a minLength: 1 constraint added, meaning empty strings ("") are no longer valid values:

    • external_auth_token (appears in two request schemas, likely create and update operations)
    • external_user_id (in a separate request schema)

    Any client currently sending empty strings for these fields will receive a validation error. This is a breaking change for clients that relied on empty strings being accepted.

  • Informational

    Remove 204 response spec from bulk_ban_users_from_guild

    The 204 response definition (with rate-limit headers) was removed from the POST /guilds/{guild_id}/bulk-ban (bulk_ban_users_from_guild) operation in the OpenAPI spec. This is a spec-only correction — the actual API likely never returns a bare 204 for this endpoint (it returns 200 with body data), so removing the erroneous response definition brings the spec closer to reality without changing real API behaviour.

  • 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.