tencent cloud

消息队列 CKafka 版

动态与公告
新功能发布记录
Broker 版本升级记录
公告
产品简介
TDMQ 产品系列介绍与选型
什么是消息队列 CKafka 版
产品优势
应用场景
技术架构
产品系列介绍
开源 Kafka 版本支持说明
与开源 Kafka 对比
高可用
使用限制
地域和可用区
相关云服务
产品计费
计费概述
价格说明
计费示例
按小时付费转包年包月
续费说明
查看消费明细
欠费说明
退费说明
快速入门
入门流程指引
准备工作
VPC 网络接入
公网域名接入
用户指南
使用流程指引
配置账号权限
创建实例
配置 Topic
连接实例
管理消息
管理消费组
管理实例
变更实例规格
配置限流
配置弹性伸缩策略
配置高级特性
查看监控和配置告警
使用连接器同步数据
实践教程
集群资源评估
客户端实践教程
日志接入
开源生态对接
替换支撑路由(旧)
迁移指南
迁移方案概述
使用开源工具迁移集群
故障处理
Topic 相关
客户端相关
消息相关
API 参考
History
Introduction
API Category
Making API Requests
Other APIs
ACL APIs
Instance APIs
Routing APIs
DataHub APIs
Topic APIs
Data Types
Error Codes
SDK 参考
SDK 概述
Java SDK
Python SDK
Go SDK
PHP SDK
C++ SDK
Node.js SDK
连接器相关 SDK
安全与合规
权限管理
网络安全
删除保护
事件记录
云 API 审计
常见问题
实例相关
Topic 相关
Consumer Group 相关
客户端相关
网络问题
监控相关
消息相关
服务协议
服务等级协议
联系我们
词汇表

Request Structure

PDF
聚焦模式
字号
最后更新时间: 2025-12-29 11:41:29

1. Service Address

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

Note: As financial availability zones and non-financial availability zones are isolated, when accessing the services in a financial availability zone (with the common parameter Region specifying a financial availability zone), it is necessary to specify a domain name of the financial availability zone, preferably in the same region as specified in Region.

Access region for financial availability zone Domain name for financial availability zone
East China (Shanghai Finance) ckafka.ap-shanghai-fsi.tencentcloudapi.com
South China (Shenzhen Finance) ckafka.ap-shenzhen-fsi.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.

帮助和支持

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

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

文档反馈