tencent cloud

消息队列 RabbitMQ 版

动态与公告
新功能发布记录
公告
产品简介
TDMQ 产品系列介绍与选型
什么是消息队列 RabbitMQ 版
产品优势
应用场景
开源托管版与 Serverless 版差异说明
开源版本支持说明
与开源 RabbitMQ 对比
高可用
使用限制
RabbitMQ 相关概念
开区地域
相关云服务
产品计费
计费概述
价格说明
计费示例
按小时付费转包年包月
续费说明
查看消费明细
欠费说明
退费说明
快速入门
入门流程指引
步骤1:准备工作
步骤2:创建 RabbitMQ 集群
步骤3:配置 Vhost
步骤4:使用 SDK 收发消息
步骤5:查询消息
步骤6:销毁资源
用户指南
使用流程指引
配置账号权限
创建集群
配置 Vhost
连接集群
管理消息
配置高级特性
管理集群
查看监控和配置告警
实践教程
实践教程使用说明
RabbitMQ 客户端实践教程
RabbitMQ 消息可靠性实践教程
RabbitMQ 支持 MQTT 协议说明
迁移集群
迁移方案概述
步骤1:购买云上实例
步骤2:迁移元数据上云
步骤3:开启双读写
API 参考(开源托管版)
API 概览
API 参考(Serverless 版)
History
Introduction
API Category
Making API Requests
Relevant APIs for RabbitMQ Serverless PAAS Capacity
RabbitMQ Serverless Instance Management APIs
Data Types
Error Codes
SDK 文档
SDK 概述
Spring Boot Starter 接入
Spring Cloud Stream 接入
Java SDK
Go SDK
Python SDK
PHP SDK
安全与合规
权限管理
网络安全
删除保护
变更记录
云 API 审计
常见问题
服务等级协议
联系我们

Request Structure

聚焦模式
字号
最后更新时间: 2025-10-30 22:05:12

1. Service Address

The API supports access from either a nearby region (at trabbit.intl.tencentcloudapi.com) or a specified region (at trabbit.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 "trabbit.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) trabbit.intl.tencentcloudapi.com
South China (Guangzhou) trabbit.ap-guangzhou.tencentcloudapi.com
East China (Shanghai) trabbit.ap-shanghai.tencentcloudapi.com
East China (Nanjing) trabbit.ap-nanjing.tencentcloudapi.com
North China (Beijing) trabbit.ap-beijing.tencentcloudapi.com
Southwest China (Chengdu) trabbit.ap-chengdu.tencentcloudapi.com
Southwest China (Chongqing) trabbit.ap-chongqing.tencentcloudapi.com
Hong Kong, Macao, Taiwan (Hong Kong, China) trabbit.ap-hongkong.tencentcloudapi.com
Southeast Asia (Singapore) trabbit.ap-singapore.tencentcloudapi.com
Southeast Asia (Jakarta) trabbit.ap-jakarta.tencentcloudapi.com
Southeast Asia (Bangkok) trabbit.ap-bangkok.tencentcloudapi.com
Northeast Asia (Seoul) trabbit.ap-seoul.tencentcloudapi.com
Northeast Asia (Tokyo) trabbit.ap-tokyo.tencentcloudapi.com
U.S. East Coast (Virginia) trabbit.na-ashburn.tencentcloudapi.com
U.S. West Coast (Silicon Valley) trabbit.na-siliconvalley.tencentcloudapi.com
South America (São Paulo) trabbit.sa-saopaulo.tencentcloudapi.com
Europe (Frankfurt) trabbit.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.

帮助和支持

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

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

文档反馈