tencent cloud

Tencent Container Registry

Release Notes and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Overview
TCR Service Levels and Capacity Limits
Strengths
Scenarios
Purchase Guide
Billing Overview
Purchase Methods
Notes on Arrears
Getting Started
Quick Start
TCR Individual Getting Started
Operation Guide
Creating an Enterprise Edition Instance
Access Configuration
Manage Image Repository
Image Distribution
Image Security
Image Cleanup
DevOps
OCI Artifacts Management
Operation Guide for TCR Individual
Terminating/Returning Instances
Use Cases
TCR Personal migration
TKE Clusters Use the TCR Addon to Enable Secret-free Pulling of Container Images via Private Network
Synchronizing Images to TCR Enterprise Edition from External Harbor
TKE Serverless Clusters Pull TCR Container Images
Image Data Synchronization and Replication Between Multiple Platforms in Hybrid Cloud
Nearby Access Through Image Synchronization Between Multiple Global Regions
Using Custom Domain Name and CCN to Implement Cross-Region Private Network Access
API Documentation
History
Introduction
API Category
Making API Requests
Instance Management APIs
Namespace APIs
Access Control APIs
Instance Synchronization APIs
Tag Retention APIs
Trigger APIs
Helm Chart APIs
Image Repository APIs
Custom Account APIs
Data Types
Error Codes
FAQs
TCR Individual Edition
TCR Enterprise Edition
Related Agreement
Service Level Agreement
Contact Us
Glossary

Request Structure

PDF
Focus Mode
Font Size
Last updated: 2025-10-30 21:57:57

1. Service Address

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

Help and Support

Was this page helpful?

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

Feedback