Available in Classic and VPC
View the list of results from running a trigger for a month.
Request
The following describes the request format for the endpoint. The request format is as follows:
| Method | URI |
|---|---|
| GET | /triggers/{triggerName}/activations |
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
|
pageSize |
Integer | Optional | Page size of the query result
|
pageNo |
Integer | Optional | Query result page number
|
start |
Integer | Optional | Timestamp of the query start time (milliseconds)
|
end |
Integer | Optional | Timestamp of the query end time (milliseconds)
|
Request example
The following is a sample request.
curl --location --request GET 'https://cloudfunctions.apigw.ntruss.com/ncf/api/v2/triggers/trg1-os/activations?platform=vpc' \
--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'
Response
The following describes the response format.
Response body
The following describes the response body.
| Field | Type | Description |
|---|---|---|
content.activations |
Object | Execution result information |
content.activations[].activationId |
String | Trigger execution result ID |
content.activations[].duration |
Integer | Time taken to execute the trigger (milliseconds) |
content.activations[].status |
String | Trigger status |
content.totalCount |
Integer | Number of execution results |
Response status codes
The following describes the response status codes.
| HTTP status code | Code | Message | Description |
|---|---|---|---|
| 400 | 80000 | INTERNAL_EXCEPTION | Request parameter error |
| 400 | 80502 | TRIGGER_PLATFORM_MISMATCH | Trigger platform parameter error |
| 403 | 80002 | SUB_ACC_NO_PERMISSION | Detailed permission error |
| 404 | 80501 | TRIGGER_NOT_FOUND | Trigger not found |
Response example
The following is a sample response.
{
"content": {
"activations": [
{
"activationId": "e251b49a25094dcd91b49a25093dcdb0",
"duration": 0,
"status": "success"
}
],
"totalCount": 1
}
}