---
title: "Youtube Reply"
method: POST
path: "/api/channels/youtube/comments/{thread_id}/reply"
tags: ["channels", "channels", "youtube"]
---

# Youtube Reply

`POST /api/channels/youtube/comments/{thread_id}/reply`

## Request

- Base URL: `https://api.dialogbrain.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.dialogbrain.com/api/channels/youtube/comments/{thread_id}/reply`
- Auth: none declared

Post a top-level comment on the video referenced by `thread_id`.

`thread_id` may be the numeric `thread.id` OR the canonical
`youtube:video:<id>`; both resolve to the same row.

Defense-in-depth on the disclosure suffix even though the
auto_reply chokepoint (Task 1.14) already ran the same check —
`ensure_disclosure` is idempotent via the `ACCEPTABLE_MARKER_RE`
recognizer. Manual replies (route hit directly without going
through auto_reply_agent) get the suffix here.

## Path parameters

- `thread_id` string, required

## Request body

- ReplyRequest
  - `text` string, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/dialogbrain/apis/dialogbrain-v2-api-gateway.md) · [All operations](https://skmtc.dev/dialogbrain/apis/dialogbrain-v2-api-gateway/llms.txt) · [OpenAPI document](https://skmtc.dev/dialogbrain/apis/dialogbrain-v2-api-gateway/revisions/d84e7dc9977d?raw)