Available in Classic and VPC
View a Cloud Functions trigger.
Request
The following describes the request format for the endpoint. The request format is as follows:
| Method | URI |
|---|---|
| GET | /triggers/{triggerName} |
Request headers
For headers common to all Cloud Functions APIs, see Cloud Functions common headers.
Request path parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
triggerName |
String | Required | Trigger name |
Request query parameters
The following describes the parameters.
| Field | Type | Required | Description |
|---|---|---|---|
platform |
String | Optional | Platform type
|
Request example
The following is a sample request.
curl --location --request GET 'https://cloudfunctions.apigw.ntruss.com/api/v2/triggers/trigger000?platform=classic' \
--header 'Content-Type: application/json' \
--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}'
Response
The following describes the response format.
Response body
The following describes the response body.
| Field | Type | Description |
|---|---|---|
content.actions |
String[] | List of actions associated with the trigger |
content.description |
String | Description of the trigger |
content.execOption |
Object | Execution option by trigger type |
content.name |
String | Trigger name |
content.resourceId |
String | Trigger's resource ID |
content.type |
String | Trigger type |
Response status codes
For response status codes common to NAVER Cloud Platform, see Ncloud API response status codes.
Response example
The following is a sample response.
{
"content": {
"actions": [
"action111"
],
"description": "",
"execOption": {
"key": "ncf_triggerOptions",
"value": [
{
"key": "cron",
"value": "*/1 * * * *"
}
]
},
"name": "trigger000",
"resourceId": "1v***",
"type": "cron"
}
}