# Create Topic Reply

`POST` `/v1/content/topics/{topic_id}/comments`

Post a reply to a community topic. Supports nesting under an existing reply. Browse the community on [Topics](https://longbridge.com/topics).

Only users who have opened a **[Longbridge account](https://longbridge.com/hk/download) and hold assets** are allowed to publish community topics and replies via Longbridge Developers API or CLI. Returns `403` otherwise.

**Body format:** Plain text only — HTML and Markdown are **not** rendered.

:::tip Tip
Stock symbols mentioned in the body (e.g. `700.HK`, `TSLA.US`) are automatically recognized and linked as related stocks by the platform.

⚠️ Do not abuse symbol linking to associate unrelated stocks. Content moderation may restrict publishing or mute the account.
:::

**Rate limit:** The first 3 replies per user per topic have no wait requirement. After that, each subsequent reply must wait an incrementally longer interval since the previous one:

| Reply # (after 3rd) | Required wait |
| ------------------- | ------------- |
| 4th | 3 s |
| 5th | 5 s |
| 6th | 8 s |
| 7th | 13 s |
| 8th | 21 s |
| 9th | 34 s |
| 10th+ | 55 s (cap) |

Exceeding the limit returns `429`.

:::warning
⚠️ Rate limit thresholds are for reference only and may be adjusted by the platform at any time.
:::

## Parameters

### Path Parameters

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `topic_id` | string | Yes | Topic ID (e.g. `6993508780031016960`) |

### Request Body

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `body` | string | Yes | Reply body. Plain text only — Markdown is not rendered. Symbols mentioned in the body are auto-linked by the platform. |
| `reply_to_id` | string | No | ID of the reply to nest under. Omit or set to `"0"` for a top-level reply. |

## Request Example

```bash
curl --request POST \
  --url 'https://openapi.longbridge.com/v1/content/topics/<topic_id>/comments' \
  --header 'Authorization: Bearer <access_token>' \
  --header 'Content-Type: application/json' \
  --data '{"body":"<body>","reply_to_id":"<reply_to_id>"}'
```

## Response

### Response Properties

| Name | Type | Required | Description |
| --- | --- | --- | --- |
| `item` | object | Yes | Created reply details |
| `└ id` | string | Yes | Reply ID |
| `└ topic_id` | string | Yes | Parent topic ID |
| `└ body` | string | No | Reply body (plain text) |
| `└ reply_to_id` | string | No | Parent reply ID; `"0"` = top-level reply |
| `└ author` | object | No | Author info |
| `└ ∟ member_id` | string | No | Author member ID |
| `└ ∟ name` | string | No | Author display name |
| `└ ∟ avatar` | string | No | Author avatar URL |
| `└ images` | object[] | No | Attached images |
| `└ ∟ url` | string | No | Original image URL |
| `└ ∟ sm` | string | No | Small thumbnail URL |
| `└ ∟ lg` | string | No | Large image URL |
| `└ likes_count` | int32 | No | Likes count |
| `└ comments_count` | int32 | No | Nested replies count |
| `└ created_at` | string | Yes | Creation time as Unix timestamp (seconds) |

### Response JSON Example

```json
{
  "code": 0,
  "message": "success",
  "data": {
    "item": {
      "id": "7001234567890123460",
      "topic_id": "6993508780031016960",
      "body": "Great analysis!",
      "reply_to_id": "0",
      "author": {
        "member_id": "10086",
        "name": "Jane Doe",
        "avatar": "https://example.com/avatar.jpg"
      },
      "images": [],
      "likes_count": 0,
      "comments_count": 0,
      "created_at": "1742002000"
    }
  }
}
```
