Querying Project Tags
Function
This API is used to query project tags.
API Calling
For details, see Calling APIs.
URI
GET /v3/{project_id}/{resource_type}/tags
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        project_id  | 
      
        Yes  | 
      
        String  | 
      
        Project ID.  | 
     
| 
        resource_type  | 
      
        Yes  | 
      
        String  | 
      
        Resource type. The value is cts-tracker.  | 
     
| 
        Parameter  | 
      
        Mandatory  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|---|
| 
        limit  | 
      
        No  | 
      
        Integer  | 
      
        Maximum records that can be returned. The value ranges from 1 to 200 (default).  | 
     
| 
        marker  | 
      
        No  | 
      
        String  | 
      
        Pagination parameter. You can use the marker value returned in the previous request as the number of the first page of records to return in this request.  | 
     
Request Parameters
None.
Response Parameters
Status code: 200
| 
        Parameter  | 
      
        Type  | 
      
        Description  | 
     
|---|---|---|
| 
        tags  | 
      
        Array of TmsTags objects  | 
      
        Tag list.  | 
     
| 
        page_info  | 
      
        PageInfo object  | 
      
        Pagination parameter.  | 
     
Example Request
None.
Example Response
Status code: 200
The request is successful.
{
  "tags" : [ {
    "key" : "key1",
    "values" : [ "value1", "value2" ]
  }, {
    "key" : "key2",
    "values" : [ "value1", "value2" ]
  } ],
  "page_info" : {
    "current_count" : "200",
    "next_marker" : "xxx"
  }
}
 Status Codes
| 
        Status Code  | 
      
        Description  | 
     
|---|---|
| 
        200  | 
      
        The request is successful.  | 
     
Error Codes
For details, see Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.