getCostRelationCodeList
- Print
- PDF
getCostRelationCodeList
- Print
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Available in Classic and VPC
View the list of cost association codes.
You can use cost association codes in the View usage (getContractUsageList, getContractUsageListByDaily) or cost(getContractDemandCostList, getProductDemandCostList) APIs.
Request
The following describes the request format for the endpoint. The request format is as follows:
Method | URI |
---|---|
GET | /cost/getCostRelationCodeList |
Request headers
For headers common to all Cost and usage APIs, see Cost and usage common headers.
Request query parameters
The following describes the parameters.
Field | Type | Required | Description |
---|---|---|---|
contractTypeCode | String | Optional | Contract type code |
productItemKindCode | String | Optional | Product item type code |
productRatingTypeCode | String | Optional | Product charge type code |
meteringTypeCode | String | Optional | Metering type code |
productCategoryCode | String | Optional | Product category code
|
responseFormatType | String | Optional | Response result format
|
Request example
The following is a sample request.
curl --location 'https://billingapi.apigw.ntruss.com/billing/v1/cost/getCostRelationCodeList?contractTypeCode=VSVR&productItemKindCode=VSVR'
--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}'
Response
The following describes the response format.
Response body
See CostRelationCodeList 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.
<?xml version="1.0" encoding="UTF-8"?>
<getCostRelationCodeListResponse>
<requestId>46ab577a-****-****-****-09d8716f0019</requestId>
<returnCode>0</returnCode>
<returnMessage>success</returnMessage>
<totalRows>2</totalRows>
<costRelationCodeList>
<costRelationCode>
<contractType>
<code>VSVR</code>
<codeName>Server(VPC)</codeName>
</contractType>
<productItemKind>
<code>VSVR</code>
<codeName>VPC Server</codeName>
</productItemKind>
<productRatingType>
<code>VSVR</code>
<codeName>VPC Server</codeName>
</productRatingType>
<meteringType>
<code>VSVR</code>
<codeName>VPC Server</codeName>
</meteringType>
<demandType>
<code>VSVR</code>
<codeName>Server (VPC)</codeName>
</demandType>
<demandTypeDetail>
<code>VSVR</code>
<codeName>VPC Server</codeName>
</demandTypeDetail>
<productDemandType>
<code>VSVR</code>
<codeName>Server(VPC)</codeName>
<regionCode/>
</productDemandType>
<productCategory>
<code>COMPUTE</code>
<codeName>Compute</codeName>
</productCategory>
</costRelationCode>
<costRelationCode>
<contractType>
<code>VSVR</code>
<codeName>Server(VPC)</codeName>
</contractType>
<productItemKind>
<code>VSVR</code>
<codeName>VPC Server</codeName>
</productItemKind>
<productRatingType>
<code>VSVR</code>
<codeName>VPC Server</codeName>
</productRatingType>
<meteringType>
<code>VSVRT</code>
<codeName>Server (VPC) Stop Usage</codeName>
</meteringType>
<demandType>
<code>VSVR</code>
<codeName>Server (VPC)</codeName>
</demandType>
<demandTypeDetail>
<code>VSVRT</code>
<codeName>Server (VPC) Stop Usage</codeName>
</demandTypeDetail>
<productDemandType>
<code>VSVR</code>
<codeName>Server(VPC)</codeName>
<regionCode/>
</productDemandType>
<productCategory>
<code>COMPUTE</code>
<codeName>Compute</codeName>
</productCategory>
</costRelationCode>
</costRelationCodeList>
</getCostRelationCodeListResponse>
Was this article helpful?