Purpose
GET
/chats/{chat_id}/topicsList forum topics in a Telegram forum-enabled supergroup.
Authentication
Send a tenant API key as Authorization: Bearer <key> or X-API-Key: <key>. Keep keys server-side and use the account slug for the connected Telegram account.
Parameters
NameInRequiredType / constraints
chat_id
path
required
integer
limit
query
optional
integer · default 50 · range 1–100
Request example
Replace the tenant, account, and resource placeholders before running this read-only request.
curl --fail-with-body \
-H "Authorization: Bearer ${DATAZ_API_KEY}" \
"https://dataz.md/gateway/v1/{tenant_slug}/accounts/{account_slug}/chats/{chat_id}/topics?limit=100"
Response schema
Documented responses
200Response model: List[Topic]List[Topic]
Response example
Representative JSON shape. The live response can include additional documented fields.
[
{
"id": "123456789012345678",
"title": "Example topic"
}
]
Errors
Common responses
401Missing or invalid tenant API key.authentication
403The tenant, account, or connected provider cannot access the requested resource.authorization
404The route or requested provider resource was not found.not found
422A path or query parameter is invalid.validation
429Rate limited; wait for the Retry-After interval before retrying.rate limit
Limits and pagination
- Use
limitto bound each response; it defaults to 50 and accepts 1–100. - Provider or demo limits can return HTTP 429. Wait for the
Retry-Afterinterval before retrying.
Related tutorials
Read-only notes
This reference page documents a public GET endpoint. Setup/token, AI, dev, internal, and mutating routes are excluded from static reference generation.