Available in Classic and VPC
Run a trigger to execute the configured action.
Request
The following describes the request format for the endpoint. The request format is as follows:
| Method | URI |
|---|---|
| POST | /ncf/api/v2/triggers/{triggerName} |
Request headers
For information about the headers common to all Cloud Functions APIs, see Cloud Functions request headers.
Request path parameters
You can use the following path parameters with your request:
| Field | Type | Required | Description |
|---|---|---|---|
triggerName |
String | Required | Trigger name |
Request query parameters
You can use the following query parameters with your request:
| Field | Type | Required | Description |
|---|---|---|---|
platform |
String | Optional | Platform type
|
Request body
The following describes the request body.
Depending on the type of the trigger, you can pass the runtime parameters of the required action in JSON format.
| Field | Type | Required | Description |
|---|---|---|---|
| User-defined | Object | Optional | Action runtime parameter |
Request example
The following is a sample request.
curl --location --request POST 'https://cloudfunctions.apigw.ntruss.com/ncf/api/v2/triggers/trg1-os' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Sub Account Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \
--header 'Content-Type: application/json' \
--data '{
"name": "Cloud Functions",
"place": "NAVER Cloud"
}'
Response
The following describes the response format.
Response body
The following describes the response body.
| Field | Type | Required | Description |
|---|---|---|---|
content.activationId |
String | - | Trigger execution result ID |
Response status codes
For information about the HTTP status codes common to all Cloud Functions APIs, see Cloud Functions response status codes.
Response example
The following is a sample response.
{
"content": {
"activationId": "e251b49a25094dcd91b49a25093dcdb0"
}
}