Post trigger external link

Available in Classic and VPC

Create or edit an external connection address that can call the trigger. Only basic and GitHub types of triggers are available.

Request

The following describes the request format for the endpoint. The request format is as follows:

Request headers

For headers common to all Cloud Functions APIs, see Cloud Functions common headers.

Request path parameters

The following describes the parameters.

Request query parameters

The following describes the parameters.

Request body

The following describes the request body.

{
   "productId" : "string",
   "productName" : "string",
   "apiName" : "string",
   "stageName" : "string",
   "authentication": "string"
}

Request example

The following is a sample request.

curl --location --request POST 'https://cloudfunctions.apigw.ntruss.com/api/v2/triggers/trg1/external-link-url' \
--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>'

{
   "productId" : "",
   "productName" : "functions",
   "apiName" : "api",
   "stageName" : "v1",
   "authentication": "IAM"
}

Response

The following describes the response format.

Response body

The following describes the response body.

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": {
        "result": "ok"
    }
}