tencent cloud

피드백

Request Structure

마지막 업데이트 시간:2024-11-27 11:09:53

    1. Service Address

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

    문의하기

    고객의 업무에 전용 서비스를 제공해드립니다.

    기술 지원

    더 많은 도움이 필요하시면, 티켓을 통해 연락 바랍니다. 티켓 서비스는 연중무휴 24시간 제공됩니다.

    연중무휴 24시간 전화 지원