News & Contents

Create Topic Reply

POSThttps://openapi.longbridge.com/v1/content/topics/{topic_id}/comments

Authorization

Signed mode: every request is signed with your App Key/Secret. Header set:

NameTypeRequiredDescription
Authorizationstring · headerRequiredThe account Access Token from the OpenAPI dashboard — passed as the raw token (no Bearer prefix) and included in the signature calculation.
X-Api-Keystring · headerRequiredYour App Key.
X-Timestampstring · headerRequiredRequest timestamp in seconds (Unix epoch).
X-Api-Signaturestring · headerRequiredHMAC-SHA256 signature. Format: HMAC-SHA256 SignedHeaders=authorization;x-api-key;x-timestamp, Signature=.

Post a reply to a community topic. Supports nesting under an existing reply. Browse the community on Topics.

Only users who have opened a Longbridge account 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

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.

>_ CLI
longbridge topic create-reply 6993508780031016960 --body "Great analysis!"

Request

Path parameters

NameTypeRequiredDescription
topic_idstringRequiredTopic ID (e.g. `6993508780031016960`)

Request body

NameTypeRequiredDescription
bodystringRequiredReply body. Plain text only — Markdown is not rendered. Symbols mentioned in the body are auto-linked by the platform.
reply_to_idstringOptionalID of the reply to nest under. Omit or set to `"0"` for a top-level reply.

Response

Response properties

NameTypeRequiredDescription
itemobjectRequiredCreated reply details
└ idstringRequiredReply ID
└ topic_idstringRequiredParent topic ID
└ bodystringOptionalReply body (plain text)
└ reply_to_idstringOptionalParent reply ID; `"0"` = top-level reply
└ authorobjectOptionalAuthor info
└ ∟ member_idstringOptionalAuthor member ID
└ ∟ namestringOptionalAuthor display name
└ ∟ avatarstringOptionalAuthor avatar URL
└ imagesobject[]OptionalAttached images
└ ∟ urlstringOptionalOriginal image URL
└ ∟ smstringOptionalSmall thumbnail URL
└ ∟ lgstringOptionalLarge image URL
└ likes_countint32OptionalLikes count
└ comments_countint32OptionalNested replies count
└ created_atstringRequiredCreation time as Unix timestamp (seconds)

Response JSON example

{
  "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"
    }
  }
}

Error code

See the Error Codes page for the full list of error codes.