tencent cloud

Serverless Cloud Function

Release Notes and Announcements
Release Notes
Announcements
User Guide
Product Introduction
Overview
Related Concepts
How It Works
Strengths
Scenarios
Related Products
Purchase Guide
Billing Overview
Billing Mode
Billable Items and Billing Modes
Function Computing Power Support
Free Tier
SCF Pricing
Billing Example
Payment Overdue
Getting Started
Creating Event Function in Console
User Guide
Quota Management
Managing Functions
Web Function Management
Log Management
Concurrence Management
Trigger Management
Function URL
A Custom Domain Name
Version Management
Alias Management
Permission Management
Running Instance Management
Plugin Management
Managing Monitors and Alarms
Network Configuration
Layer Management
Execution Configuration
Extended Storage Management
DNS Caching Configuration
Resource Managed Mode Management
Near-Offline Resource Hosting Model
Workflow
Triggers
Trigger Overview
Trigger Event Message Structure Summary
API Gateway Trigger
COS Trigger
CLS Trigger
Timer Trigger
CKafka Trigger
Apache Kafka Trigger
MQTT Trigger
Trigger Configuration Description
MPS Trigger
CLB Trigger Description
TencentCloud API Trigger
Development Guide
Basic Concepts
Testing a Function
Environment Variables
Dependency Installation
Using Container Image
Error Types and Retry Policies
Dead Letter Queue
Connecting SCF to Database
Automated Deployment
Cloud Function Status Code
Common Errors and Solutions
Developer Tools
Serverless Web IDE
Calling SDK Across Functions
Third-Party Tools
Code Development
Python
Node.js
Golang
PHP
Java
Custom Runtime
Deploying Image as Function
Web Framework Development
Deploying Framework on Command Line
Quickly Deploying Egg Framework
Quickly Deploying Express Framework
Quickly Deploying Flask Framework
Quickly Deploying Koa Framework
Quickly Deploying Laravel Framework
Quickly Deploying Nest.js Framework
Quickly Deploying Next.js Framework
Quickly Deploying Nuxt.js Framework
Quickly Deploying Django Framework
Use Cases
Overview
Solutions with Tencent Cloud Services
Business Development
TRTC Practices
COS Practices
CKafka Practice
CLS
CLB Practice
MPS
CDN
CDWPG
VOD
SMS
ES
Scheduled Task
Video Processing
Success Stories
Tencent Online Education
Online Video Industry
Tencent Online Education
Best Practice of Tencent IEG Going Global
API Documentation
History
Introduction
API Category
Making API Requests
Other APIs
Namespace APIs
Layer Management APIs
Async Event Management APIs
Trigger APIs
Function APIs
Function and Layer Status Description
Data Types
Error Codes
SDK Documentation
FAQs
General
Web Function
Billing FAQs
Network FAQs
Log FAQs
SCF utility class
Event Handling FAQs
API Gateway Trigger FAQs
Related Agreement
Service Level Agreement
Contact Us
Glossary
ドキュメントServerless Cloud FunctionAPI DocumentationMaking API RequestsRequest Structure

Request Structure

PDF
フォーカスモード
フォントサイズ
最終更新日: 2025-10-30 21:54:40

1. Service Address

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

前の記事へ: API Category次の記事へ: Common Params

ヘルプとサポート

この記事はお役に立ちましたか？

フィードバック