tencent cloud

Tencent Cloud Organization

  • Product Introduction
  • Purchase Guide
  • Operation Guide
    • Console Overview
    • Organization Settings
    • Department Management
    • Member Account Management
    • Member Finance Management
    • Member Access Management
    • Resource Management
    • Member Audit
    • Identity Center Management
  • API Documentation
    • History
    • Introduction
    • API Category
    • Making API Requests
    • Organization Settings APIs
    • Department and Member Management APIs
    • ListOrganizationIdentity
    • Unified Member Login APIs
    • Organization Service Management APIs
    • Organization Management Policy APIs
    • Resource Sharing APIs
    • Identity Center Management APIs
    • Identity Center User Management APIs
    • Identity Center User Group Management APIs
    • Identity Center Management SCIM Synchronization APIs
    • Identity Center Single Sign-On Management APIs
    • Identity Center Permission Configuration Management APIs
    • Identity Center Multi-Account Authorization Management APIs
    • Identity Center Sub-User Synchronization Management APIs
    • Data Types
    • Error Codes
    • TCO API 2018-12-25
  • Related Agreement
  • FAQs
  • Glossary

Request Structure

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2025-10-30 21:52:50

1. Service Address

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

Ajuda e Suporte

Esta página foi útil?

comentários