tencent cloud

消息队列 MQTT 版

动态与公告
新功能发布记录
产品简介
TDMQ 产品系列介绍与选型
什么是消息队列 MQTT 版
应用场景
技术架构
产品系列
MQTT 协议兼容说明
开源对比
高可用
产品约束与使用配额
基本概念
开服地域
购买指南
计费概述
续费说明
查看消费明细
欠费说明
退费说明
快速入门
入门流程指引
准备工作
公网接入
VPC 网络接入
用户指南
使用流程指引
配置账号权限
新建集群
管理 Topic
连接集群
查询消息
管理客户端
管理集群
查看监控和配置告警
数据集成
集成数据到云函数 SCF
集成数据到 CKafka
集成数据到 RocketMQ
开发指南
MQTT 5 高级特性
数据面 HTTP 接口说明
配置自定义域名
配置 SQL 过滤
配置点对点订阅
MQTT over QUIC
管理客户端订阅
消息增强规则
实践教程
MQTT 客户端开发注意事项
可观测能力
Topic 与通配符订阅
API 参考
History
Introduction
API Category
Making API Requests
Cluster APIs
Topic APIs
Authorization Policy APIs
User APIs
Client APIs
Message Enhancement Rule APIs
Message APIs
Data Types
Error Codes
SDK 参考
接入点格式
Java SDK
C SDK
Javascript/Node.JS/小程序
Go SDK
iOS SDK
JavaScript SDK
Dart SDK
Python SDK
.NET
安全与合规
权限管理
常见问题
相关协议
隐私协议
数据处理和安全协议
消息队列 MQTT 版服务等级协议
联系我们

Request Structure

聚焦模式
字号
最后更新时间: 2026-01-08 19:47:20

1. Service Address

The API supports access from either a nearby region (at mqtt.intl.tencentcloudapi.com) or a specified region (at mqtt.ap-guangzhou.tencentcloudapi.com for Guangzhou, for example).

We recommend using the domain name to access the nearest server. When you call an API, the request is automatically resolved to a server in the region nearest to the location where the API is initiated. For example, when you initiate an API request in Guangzhou, this domain name is automatically resolved to a Guangzhou server, the result is the same as that of specifying the region in the domain like "mqtt.ap-guangzhou.tencentcloudapi.com".

Note: For latency-sensitive businesses, we recommend that you specify the region in the domain name.

Tencent Cloud currently supports the following regions:

Hosted region Domain name
Local access region (recommended, only for non-financial availability zones) mqtt.intl.tencentcloudapi.com
South China (Guangzhou) mqtt.ap-guangzhou.tencentcloudapi.com
East China (Shanghai) mqtt.ap-shanghai.tencentcloudapi.com
East China (Nanjing) mqtt.ap-nanjing.tencentcloudapi.com
North China (Beijing) mqtt.ap-beijing.tencentcloudapi.com
Southwest China (Chengdu) mqtt.ap-chengdu.tencentcloudapi.com
Southwest China (Chongqing) mqtt.ap-chongqing.tencentcloudapi.com
Hong Kong, Macao, Taiwan (Hong Kong, China) mqtt.ap-hongkong.tencentcloudapi.com
Southeast Asia (Singapore) mqtt.ap-singapore.tencentcloudapi.com
Southeast Asia (Jakarta) mqtt.ap-jakarta.tencentcloudapi.com
Southeast Asia (Bangkok) mqtt.ap-bangkok.tencentcloudapi.com
Northeast Asia (Seoul) mqtt.ap-seoul.tencentcloudapi.com
Northeast Asia (Tokyo) mqtt.ap-tokyo.tencentcloudapi.com
U.S. East Coast (Virginia) mqtt.na-ashburn.tencentcloudapi.com
U.S. West Coast (Silicon Valley) mqtt.na-siliconvalley.tencentcloudapi.com
South America (São Paulo) mqtt.sa-saopaulo.tencentcloudapi.com
Europe (Frankfurt) mqtt.eu-frankfurt.tencentcloudapi.com

2. Communications Protocol

All the Tencent Cloud APIs communicate via HTTPS, providing highly secure communication tunnels.

3. Request Methods

Supported HTTP request methods:

  • POST (recommended)
  • GET

The Content-Type types supported by POST requests:

  • application/json (recommended). The TC3-HMAC-SHA256 signature algorithm must be used.
  • application/x-www-form-urlencoded. The HmacSHA1 or HmacSHA256 signature algorithm must be used.
  • multipart/form-data (only supported by certain APIs). You must use TC3-HMAC-SHA256 to calculate the signature.

The size of a GET request packet is up to 32 KB. The size of a POST request is up to 1 MB when the HmacSHA1 or HmacSHA256 signature algorithm is used, and up to 10 MB when TC3-HMAC-SHA256 is used.

4. Character Encoding

Only UTF-8 encoding is used.

帮助和支持

本页内容是否解决了您的问题?

填写满意度调查问卷,共创更好文档体验。

文档反馈