HTTP API Overview and Limitations
Last updated:2026-01-30 14:59:40
Overview
TDMQ for MQTT provides API interfaces based on the HTTP protocol, supporting features such as querying client online status and publishing MQTT messages. Send HTTPS/HTTP GET or POST requests to the server address, and include corresponding request parameters according to the specific interface instructions. TDMQ for MQTT will return processing results based on the request status. Interface calls are subject to flow control restrictions, and each call consumes the cluster's TPS capacity. It is particularly suitable for scenarios requiring management of large-scale devices (such as millions of devices), enabling efficient communication through HTTP data stream interfaces.
For the specific method and instructions on calling the HTTP API, refer to the following linked document.
Common Request Parameters
Parameter | Description | Example |
instance-access-point | The instance endpoint address can be obtained from the Cluster Management > Basic Information page in the console. | mqtt-xxxx-public.mqtt.tencenttdmq.com |
client_id | Client unique identifier ClientId. For specific specification definitions, refer to Client Identifier (ClientID) | curl001 |
Use Limits
Description | Limit |
Supported protocol versions | HTTP 1.0 and HTTP 1.1 protocols Supports HTTP and HTTPS, where HTTPS is recommended to be used with certificate authentication. |
Request Method | The query interface supports GET/POST. The message publishing interface supports POST. |
Interface Specifications | Querying the client status interface is equivalent to a message publication with QoS=0. The query frequency is subject to the instance QPS Quota constraints. The message publishing interface supports setting the QoS (default QoS=1) and Retained flags. For details, refer to Billing Overview |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback