Obtaining Application Details Based on the Application ID
Function
This API is used to obtain application details based on the application ID.
URI
GET /v3/{project_id}/cas/applications/{application_id}
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Tenant's project ID. See Obtaining a Project ID. |
application_id |
Yes |
String |
Application ID. See Obtaining All Applications. |
Request
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
Content-Type |
Yes |
String |
Message body type (format). Default value: application/json;charset=utf8. |
X-Auth-Token |
Yes |
String |
API calling can be authenticated using a token or AK/SK. If you use a token, this parameter is mandatory and must be set to the token. For details about how to obtain a token, see Obtaining a User Token. |
Response
Parameter |
Type |
Description |
---|---|---|
id |
String |
Application ID. |
name |
String |
Application name. |
description |
String |
Application description. |
creator |
String |
Application creator. |
project_id |
String |
Project ID. |
enterprise_project_id |
String |
Enterprise project ID. |
create_time |
Integer |
Application creation time. |
update_time |
Integer |
Application update time. |
component_count |
Integer |
Number of components deployed in an application. |
labels |
Array of objects |
Label. You can use TMS to filter resources by labels. See Table 4. |
Example Request
None
Example Response
{ "id": "e6129197-f9ca-4d60-b84d-a5e71cd2d317", "name": "app-test-0317_03", "description": "", "project_id": "063a3158b1a34710b36ad208b9497d00", "creator": "ss-test", "create_time": 1679036601735, "update_time": 1679036601735, "labels": null, "component_count": 0 }
Status Code
Status Code |
Description |
---|---|
200 |
OK |
400 |
Bad Request |
404 |
Not Found |
500 |
Internal Server Error |
Error Code
The error code format is SVCSTG.00100.[Error_ID], for example, SVCSTG.00100400. For details, see ServiceStage Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot