News & Contents
Authorization
Signed mode: every request is signed with your App Key/Secret. Header set:
| Name | Type | Required | Description |
|---|---|---|---|
Authorization | string · header | Required | The account Access Token from the OpenAPI dashboard — passed as the raw token (no Bearer prefix) and included in the signature calculation. |
X-Api-Key | string · header | Required | Your App Key. |
X-Timestamp | string · header | Required | Request timestamp in seconds (Unix epoch). |
X-Api-Signature | string · header | Required | HMAC-SHA256 signature. Format: HMAC-SHA256 SignedHeaders=authorization;x-api-key;x-timestamp, Signature=. |
Create a new community topic on Topics. Two content types are supported:
| Type | title |
body format |
Notes |
|---|---|---|---|
post (default) |
Optional | Plain text only | Markdown syntax (e.g. **bold**, # heading) is NOT rendered — it appears as literal characters, similar to a tweet. |
article |
Required | Markdown | The server converts Markdown to HTML for display. Supports headers, tables, bold, code blocks, etc. |
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.
Tip
Stock symbols mentioned in the body (e.g. 700.HK, TSLA.US) are automatically recognized and linked as related stocks by the platform. Use tickers to associate additional symbols not explicitly mentioned in the body.
⚠️ Do not abuse symbol linking to associate unrelated stocks. Content moderation may restrict publishing or mute the account.
Rate limit: Max 3 topics per user per minute and 10 per 24 hours. Exceeding the limit returns 429.
Warning
⚠️ Rate limit thresholds are for reference only and may be adjusted by the platform at any time.
Request
Request body
| Name | Type | Required | Description |
|---|---|---|---|
title | string | Optional | Topic title. Required when `topic_type` is `article`; optional for `post`. |
body | string | Required | Topic body. - For `post`: plain text only — Markdown is not rendered. - For `article`: Markdown is supported. |
topic_type | string | Optional | Content type: `post` (plain text, default) or `article` (Markdown). |
tickers | array | Optional | Related security symbols, format `{symbol}.{market}` (e.g. `["AAPL.US", "700.HK"]`). Maximum 10. **Note:** Symbols mentioned in the body (e.g. `700.HK`, `TSLA.US`) are automatically recognized and linked by the platform. Use `tickers` to associate additional symbols not explicitly mentioned in the body. |
hashtags | array | Optional | Hashtag names (e.g. `["earnings", "fed"]`). Maximum 1. |
Response
Response properties
| Name | Type | Required | Description |
|---|---|---|---|
item | object | Required | Newly created topic details |
└ id | string | Required | Topic ID |
└ title | string | Optional | Topic title |
└ description | string | Optional | Plain-text summary (auto-generated from body) |
└ body | string | Optional | Full body text (Markdown for `article`) |
└ topic_type | string | Optional | Topic type. One of `article`, `post` |
└ tickers | string[] | Optional | Associated security symbols |
└ hashtags | string[] | Optional | Associated hashtag names |
└ images | object[] | Optional | Image list |
└ ∟ url | string | Optional | Original image URL |
└ ∟ sm | string | Optional | Small thumbnail URL |
└ ∟ lg | string | Optional | Large thumbnail URL |
└ likes_count | int32 | Optional | Number of likes |
└ comments_count | int32 | Optional | Number of replies |
└ views_count | int32 | Optional | Number of views |
└ shares_count | int32 | Optional | Number of shares |
└ detail_url | string | Optional | Direct URL to the topic |
└ author | object | Optional | Author information |
└ ∟ member_id | string | Optional | Author member ID |
└ ∟ name | string | Optional | Author display name |
└ ∟ avatar | string | Optional | Author avatar URL |
└ created_at | string | Required | Unix timestamp (seconds) when the topic was created |
└ updated_at | string | Optional | Unix timestamp (seconds) of last update |
Response JSON example
{
"code": 0,
"message": "success",
"data": {
"item": {
"id": "39304657",
"title": "My View on AAPL",
"topic_type": "article",
"tickers": [
"AAPL.US"
],
"hashtags": [
"earnings"
],
"created_at": "1742000000"
}
}
}Error code
See the Error Codes page for the full list of error codes.