Class ThreadMessageResource

constructor

• new ThreadMessageResource(http: HttpClient): ThreadMessageResource

  Parameters

  • http: HttpClient

  Returns ThreadMessageResource

Readonlyreactions

delete

• delete(message: string): Promise<void>

  Delete a thread message Permanently removes the specified message from its thread. This action cannot be undone. A regular user may only delete messages they authored. Service-to-service callers with elevated (all_powerful) scope may delete any message in a thread they can access. Returns 403 Forbidden when the caller does not own the message.

  Parameters

  • message: string

    ID of the message to delete (msg_...).

  Returns Promise<void>

  Empty body. The server responds with HTTP 204 No Content on success.

replace

• replace(message: string, input: { content?: string }): Promise<Message>

  Update a thread message Edits the content of an existing thread message and returns the updated message object. A regular user may only edit messages they authored. Service-to-service callers with elevated (all_powerful) scope may edit any accessible message without an ownership check. Returns 403 Forbidden when the caller does not own the message.

  Parameters

  • message: string

    ID of the message to update (msg_...).

  • input: { content?: string }

    Request body.

    • Optionalcontent?: string

      Replacement text content for the message. Omit to leave the content unchanged.

  Returns Promise<Message>

  The updated message object reflecting the new content.

replies

• replies(
      message: string,
      params?: {
          afterCursor?: string;
          beforeCursor?: string;
          limit?: number;
          tree?: boolean;
      },
  ): Promise<PaginatedReplies>

  List replies to a thread message Returns a cursor-paginated list of reply messages for the specified thread message. By default only direct (first-level) replies are returned. Set tree to true to retrieve the full nested reply tree in a flat list, ordered by creation time ascending. The authenticated user must have access to the thread that contains the message. If the message belongs to a team-scoped thread, the viewer is automatically scoped to that team before the query executes. Use before_cursor and after_cursor together with limit to page through large reply threads. The has_more field in the response indicates whether additional pages exist.

  Parameters

  • message: string

    ID of the thread message to fetch replies for (msg_...).

  • Optionalparams: { afterCursor?: string; beforeCursor?: string; limit?: number; tree?: boolean }

    Query parameters.

    • OptionalafterCursor?: string

      Opaque pagination cursor. Returns replies created after this point. Obtain from after_cursor in a previous response.

    • OptionalbeforeCursor?: string

      Opaque pagination cursor. Returns replies created before this point. Obtain from before_cursor in a previous response.

    • Optionallimit?: number

      Maximum number of replies to return per page. Defaults to 20.

    • Optionaltree?: boolean

      When true, returns all replies in the nested reply tree (flattened). When false or omitted, returns only direct replies to the message.

  Returns Promise<PaginatedReplies>

  Cursor-paginated list of reply messages for the requested thread message.