New: MCP server monitoring is live. Start free trial
DiscordSchemaBehavioral

Response schema changed for GET /channels/{channel_id}/messages (GuildRoleResponse)

Affected surface
GET /channels/{channel_id}/messages
Affected field
GuildRoleResponse

What changed

Response schema changed for GET /channels/{channel_id}/messages (GuildRoleResponse) Affected surface: GET /channels/{channel_id}/messages. Root cause: schema `GuildRoleResponse`. Detected at Sat, 06 Jun 2026 01:07:36 UTC UTC.

Diff

{
  "path": "GET /channels/{channel_id}/messages",
  "removed_fields": [
    "description"
  ],
  "schema_path": "schema GuildRoleResponse"
}

Likely impact

The contract still holds, but observable behavior shifted — defaults, response timing, or rate-limit shaping. Existing code keeps compiling and most calls keep working, but edge cases may differ. Worth a sanity check.

Diff your serializers against the new schema. The diff above shows what moved.

Catch changes like this on every API you depend on.

Intello monitors 100+ APIs and tells you the moment something changes — before it breaks production.