Invokes a function.
Try it now
Test
RAM authorization
|
Action |
Access level |
Resource type |
Condition key |
Dependent action |
|
fc:InvokeFunction |
create |
*All Resource
|
None | None |
Request syntax
POST /2023-03-30/functions/{functionName}/invocations HTTP/1.1
Path Parameters
|
Parameter |
Type |
Required |
Description |
Example |
| functionName |
string |
Yes |
The function name. |
my-func |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| qualifier |
string |
No |
The function version or alias. |
LATEST |
| x-fc-invocation-type |
string |
No |
The function invocation type. Valid values: Sync and Async. |
Sync |
| x-fc-log-type |
string |
No |
The type of log to return for the function invocation. Valid values: None and Tail. |
Tail |
| body |
string |
No |
The function invocation parameters. |
event |
| x-fc-async-task-id |
string |
No |
The ID of the asynchronous task. You must enable the asynchronous task feature to use this parameter. Note
When you use an SDK, set this parameter to a business-related ID. This helps you manage the task execution. For example, a video processing function can use the video filename as the invocation ID. Use this ID to check whether the video is processed or to stop the processing task. The ID must start with a letter or an underscore (_). It can contain letters, digits, underscores (_), and hyphens (-). The ID can be up to 128 characters long. If you do not specify an ID for an asynchronous invocation, the system automatically generates one. |
test-id |
Response elements
|
Element |
Type |
Description |
Example |
|
string |
The function invocation response. |
response |
Examples
Success response
JSON format
"response"
Error codes
See Error Codes for a complete list.
Release notes
See Release Notes for a complete list.