Expose NSFW status directly on thread channel object in API responses

[scrazzz]

Currently, the Discord API does not expose the nsfw field for thread channels. Instead, this information can only be inferred from the parent channel’s nsfw property.

This creates a limitation when using the REST API in contexts where only the thread object is provided (e.g., in interaction payloads from message commands). In these cases, the thread channel object looks like this:

{
  "id": "1413248532516700202",
  "guild_id": "219974358674833408",
  "parent_id": "315889598960238592",
  "name": "JAV Top 10 Lists",
  "type": 11,
  "thread_metadata": {
    "archived": false,
    "auto_archive_duration": 10080,
    "archive_timestamp": "2025-09-04T22:29:56.405000+00:00",
    "create_timestamp": "2025-09-04T19:45:07.040000+00:00",
    "locked": false
  },
  ...
}

As shown, there is no nsfw field on the thread object. Since this is a user-installed app, it cannot GET the parent channel (the app is not authorized to access the guild). This is the only data available in the interaction payload for channel, which makes it impossible to determine if the thread is NSFW.

According to the documentation on NSFW Threads, threads can be NSFW if their parent channel is NSFW. However, this is not reflected directly in the API response for the thread.

Request: Expose an nsfw field on thread channel object in API responses, similar to other channel types, either:

• as a top-level nsfw field (like other channels), or
• as part of thread_metadata (if that makes more sense internally).

Top-level field:

{
  "id": "1413248532516700202",
  "name": "JAV Top 10 Lists",
  "type": 11,
  "nsfw": true,
  "thread_metadata": { ... }
}

Or inside thread_metadata:

{
  "id": "1413248532516700202",
  "name": "JAV Top 10 Lists",
  "type": 11,
  "thread_metadata": {
    "archived": false,
    "nsfw": true,
    "auto_archive_duration": 10080,
    "archive_timestamp": "2025-09-04T22:29:56.405000+00:00",
    "create_timestamp": "2025-09-04T19:45:07.040000+00:00",
    "locked": false
  }
}