Post trigger

Prev Next

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 /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
  • vpc (default) | classic

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 '<See below>'
{
    "name": "Cloud Functions",
    "place": "NAVER Cloud"
}

Response

The following describes the response format.

Response body

The following describes the response body.

Field Type Description
content.activationId String Trigger execution result ID

Response status codes

The following describes the response status codes.

HTTP status code Code Message Description
400 80502 TRIGGER_PLATFORM_MISMATCH Platform parameter error
400 80511 TRIGGER_INVALID_RUNTIME_PARAMS Request body error
400 80512 TRIGGER_INVOKE_FAIL Unable to execute because no action is associated with the trigger
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": {
        "activationId": "e251b49a25094dcd91b49a25093dcdb0"
    }
}