# Transcripts

A transcript is the permanent record of a closed conversation, written before its channel is deleted; these routes list and read them, and this page describes the logging message and the signed transcript page.

Every conversation leaves a transcript, however it was closed: through `DELETE /integrations/{id}/channels/{channel_id}`, through `DELETE /channels/{channel_id}`, by a member deleting the channel in the client, or by the conversion that created the integration (each channel the conversion swept away leaves one too).

## The transcript object

| Field | Type | Description |
|---|---|---|
| `id` | snowflake | The transcript id. |
| `channel_id` | snowflake | The id the conversation channel had. The channel no longer exists. |
| `channel_name` | string | The channel's name when it closed. |
| `topic` | ?string | The conversation's description, or `null`. |
| `opened_at` | ISO 8601 timestamp | When the channel was created. |
| `closed_at` | ISO 8601 timestamp | When it was closed. |
| `closed_by` | ?snowflake | Who closed it: the integration's bot for `api`, the member for `client`, the account that confirmed the conversion for `conversion`. |
| `closed_via` | string | `api` (the secret key), `client` (a member of the server, in the client) or `conversion` (swept when the server was converted). |
| `message_count` | integer | How many messages the transcript holds. |
| `participants` | array | Everyone who wrote in the conversation, plus every talker admitted to it even if they never spoke. Each entry is `{id, username, avatar, kind}`, where `kind` is `user` (a member of the server), `talker` or `bot`. |
| `log_message_id` | ?snowflake | The message in `logging` that records this transcript, or `null` if it could not be posted. |
| `url` | string | The signed link to the transcript page, the same link the logging message carries. |

Timestamps look like `2026-09-23T10:31:12.000000+00:00`.

## List transcripts

`GET /integrations/{id}/transcripts`

Answers transcript objects (without `messages`), newest first.

| Query | Description |
|---|---|
| `before` | Only transcripts with an id lower than this one. Pass the last id of the previous page to page backwards. |
| `limit` | 1 to 100. Defaults to 50; any value outside 1 to 100 also means 50. |

```sh
curl -s "https://discord.community/api/v9/integrations/@me/transcripts?limit=20" -H "Authorization: Bot $KEY"
```

## Get one transcript

`GET /integrations/{id}/transcripts/{transcript_id}`

Answers the transcript object plus `messages`, oldest first. A transcript that does not exist or belongs to another integration answers `404` with `{"message": "Unknown Transcript", "code": 0}`.

Each message:

| Field | Type | Description |
|---|---|---|
| `id` | snowflake | The message id. Like every snowflake it encodes when the message was sent. |
| `author` | user | The author as a Discord user object, as it was when the conversation closed. |
| `content` | string | The text. |
| `attachments` | array | Discord attachment objects (`id`, `filename`, `size`, `url`, ...). |
| `embeds` | array | Discord embed objects. |
| `type` | integer | The Discord message type (`0` default, `19` reply). |
| `edited_timestamp` | ?ISO 8601 timestamp | When it was last edited, or `null`. |
| `message_reference` | ?object | The Discord message reference for a reply, or `null`. |

```sh
curl -s https://discord.community/api/v9/integrations/@me/transcripts/1290000000000000999 -H "Authorization: Bot $KEY"
```

```json
{
  "id": "1290000000000000999",
  "channel_id": "1290000000000000001",
  "channel_name": "order-4471",
  "topic": "Customer asks where order 4471 is. Priority: normal.",
  "opened_at": "2026-09-23T10:05:00.000000+00:00",
  "closed_at": "2026-09-23T10:31:12.000000+00:00",
  "closed_by": "1287654321098765433",
  "closed_via": "api",
  "message_count": 2,
  "participants": [
    { "id": "1290000000000000050", "username": "Dana", "avatar": null, "kind": "talker" },
    { "id": "1100000000000000007", "username": "sam", "avatar": null, "kind": "user" }
  ],
  "log_message_id": "1290000000000001000",
  "url": "https://discord.community/integrations/transcripts/1290000000000000999?sig=Qm9ndXNTaWduYXR1cmU",
  "messages": [
    {
      "id": "1290000000000000101",
      "author": { "id": "1290000000000000050", "username": "Dana", "global_name": "Dana", "discriminator": "0", "avatar": null, "bot": false },
      "content": "Hi, my order 4471 has not arrived yet.",
      "attachments": [],
      "embeds": [],
      "type": 0,
      "edited_timestamp": null,
      "message_reference": null
    },
    {
      "id": "1290000000000000102",
      "author": { "id": "1100000000000000007", "username": "sam", "global_name": "Sam", "discriminator": "0", "avatar": null, "bot": false },
      "content": "It left the warehouse this morning, tracking is **AC123456**.",
      "attachments": [],
      "embeds": [],
      "type": 0,
      "edited_timestamp": null,
      "message_reference": null
    }
  ]
}
```

## The logging message

When a conversation closes, Blisscord (the system account) posts one message in the integration's `logging` channel. It carries a single embed:

| Part | Content |
|---|---|
| Title | `Conversation closed: #<channel name>` |
| Description | The topic, or `(no description)` |
| Field `Channel` | The channel id |
| Field `Messages` | The message count |
| Field `Closed by` | The closer's username, `the integration` when no closer is known, or `the server conversion` |
| Fields `Opened` and `Closed` | Times like `2026-09-23 10:05 UTC` |
| Field `Participants` | Participant usernames separated by commas, or `nobody` |
| Field `Transcript` | The signed link to the transcript page |
| Footer | `Transcript <transcript id>` |

Your bot receives it as an ordinary `MESSAGE_CREATE` in `logging`, and `log_message_id` on the transcript points at it.

## The transcript page

The link in the logging message, also returned as `url`, opens a page on the Blisscord site:

```
https://discord.community/integrations/transcripts/{transcript_id}?sig=<signature>
```

It shows the integration and server, the channel name and topic, when it was opened and closed and by whom, the participants, and every message with its attachments and embeds.

Opening it needs **both** of these:

- **The signed link.** The signature is tied to the transcript id and never expires. A changed or truncated link answers "This link is not valid".
- **A signed-in Blisscord account that is a member of the integration's server**, or platform staff. Someone who is not signed in is asked to log in and returns to the page afterwards; a signed-in account that is not a member is told it cannot view the transcript.

So a link that leaks outside your team shows nothing on its own. To show transcripts inside your own product, read them with the secret key through the routes above instead.
