tencent cloud

Event Bridge

Release Notes and Announcements
Release Notes
[July 19, 2024] Solution to CLS Billing Issues for EB Topics
User Tutorial
Product Introduction
Overview
Basic Concepts
Strengths
Use Cases
Limits
Purchase Guide
Billing Overview
Product Pricing
Overdue Payments and Service Suspension
Getting Started
Activating EventBridge
Quickly Delivering Custom Events
Quickly Configuring Cloud Monitor Event Alarm Push
Quickly Configuring Cloud Monitor Event Alarm Push
Event Source
Overview
Tencent Cloud Service Event Source
Event Structure
Connector
Event
Event Structure
Custom Event
Tencent Cloud Service Event
Event Bus
Overview
Creating Event Bus
Managing Event Bus
Linkage Tracing
Event Rule
Overview
Event Pattern
Creating Event Rule
Managing Event Rule
Configuring Data Conversion
Event Target
SCF Target
CLS Log Target
Message Push Target
CKafka Target
Practical Tutorial
Migrating Event Alarm
Real-Time Oceanus Alarm Message Push
Automatic Backup and Restart of Exceptional CVM Instance
Planning a EventBridge-based Midplatform for a Retail Business
API Documentation
History
Introduction
API Category
Making API Requests
Delivery Target APIs
Event Bus APIs
Event Rule APIs
Event Connector APIs
Data Transformer APIs
Event Storage APIs
Data Types
Error Codes
FAQs
Concept
Alarm
Billing
Contact Us
EB Policy
Privacy Policy
Data Processing And Security Agreement

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2025-11-13 20:52:31

1. Service Address

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

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback