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 name of the function. |
my-func |
Request parameters
|
Parameter |
Type |
Required |
Description |
Example |
| qualifier |
string |
No |
The version or alias of the function. |
LATEST |
| x-fc-invocation-type |
string |
No |
The function invoke type. Valid values: Sync and Async. |
Sync |
| x-fc-log-type |
string |
No |
The log type returned for function invoke. Valid values: None and Tail. |
Tail |
| body |
string |
No |
The parameters for function invoke. |
event |
| x-fc-async-task-id |
string |
No |
The ID of the asynchronous task. You must enable asynchronous tasks in advance. Note
We recommend that you set a business-related ID when you use the SDK to invoke the function, which facilitates subsequent operations on the execution. For example, a video processing function can use the video file name as the invoke ID, through which you can check whether the video processing is complete or stop the video processing. The ID must start with an uppercase or lowercase letter or an underscore (), and can contain uppercase and lowercase letters, digits (0-9), underscores (), and hyphens (-). It can be up to 128 characters in length. If you do not specify an ID for the asynchronous invoke, the system automatically generates one. |
test-id |
Response elements
|
Element |
Type |
Description |
Example |
|
string |
The function invoke 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.