View traffic profile
- Print
- PDF
View traffic profile
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic and VPC
Create a traffic profile (domain) according to the specified conditions.
Request
The following describes the request format for the endpoint. The request format is as follows:
Method | URI |
---|---|
GET | /domains |
Request headers
For headers common to all Traffic profile APIs, see Traffic profile API common headers.
Request query parameters
The following describes the parameters.
Field | Type | Required | Description |
---|---|---|---|
page | Integer | Optional | Page number of the paged results
|
size | Integer | Optional | Number of results to display on a page
|
name | String | Optional | Profile name |
Request example
The following is a sample request.
curl --location --request GET 'https://globaltrafficmanager.apigw.ntruss.com/gtm/v1/domains?page=0&size=1' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}'
Response
The following describes the response format.
Response body
See ProfileListResponse for 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": [
{
"sid": 14***,
"name": "profile.ncloudgtm.com",
"delYn": false,
"policyId": ****,
"policyName": "policy",
"lbType": "ROUND_ROBIN",
"status": "SUCCESS"
}
],
"pageable": {
"sort": {
"sorted": true,
"unsorted": false,
"empty": false
},
"pageNumber": 0,
"pageSize": 1,
"offset": 0,
"paged": true,
"unpaged": false
},
"last": true,
"totalPages": 1,
"totalElements": 1,
"sort": {
"sorted": true,
"unsorted": false,
"empty": false
},
"first": true,
"number": 0,
"numberOfElements": 1,
"size": 1,
"empty": false
}
Was this article helpful?