Edit traffic profile

Prev Next

Available in Classic and VPC

Edit the traffic profile (domain) information according to the user-defined conditions.

Request

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

Method URI
PUT /domains/{domainId}

Request headers

For headers common to all Traffic profile APIs, see Traffic profile API common headers.

Request path parameters

The following describes the parameters.

Field Type Required Description
domainId Integer Required Profile ID

Request syntax

The request syntax is as follows.

{
    "policyId": 1,
    "ttl": 300,
    "claRegion": "claRegion"
}

Request body

See ProfileRequest for the request body.

Request example

The following is a sample request.

curl --location --request PUT 'https://globaltrafficmanager.apigw.ntruss.com/gtm/v1/domains/14***' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \
--header 'Content-Type: application/json' \
--data '{
    "policyId": ****,
    "ttl": 400,
    "claRegion": "KR"
}'

Response

The following describes the response format.

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.

14***

Error code example

The following is a sample error code.

{
  "result": "FAIL",
  "error": {
    "errorCode": "05X000",
    "message": "Invalid value.<br>Hover your mouse over the displayed area to see the details in a tooltip.",
    "devMessage": "Invalid value.",
    "moreInfo": {
      "validationInfo": [
        {
          "fieldPath": "policyId",
          "msg": "You don't have permissions for the policy or the policy doesn't exist."
        }
      ],
      "timestamp": "2022-11-16T18:45:06.451+09:00"
    }
  }
}