Querying Service Details
Function
This API is used to query the details of a service.
The API can be called using both the global endpoint and region-specific endpoints.
Authorization Information
You do not need to obtain permissions to call this API.
URI
GET /v3/services/{service_id}
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| service_id | Yes | String | ID of the service to be queried. |
Request Parameters
| Parameter | Mandatory | Type | Description |
|---|---|---|---|
| Content-Type | Yes | String | Fill application/json;charset=utf8 in this field. |
| X-Auth-Token | Yes | String | IAM user token (no special permission requirements). |
Response Parameters
| Parameter | Type | Description |
|---|---|---|
| Object | Service information. |
| Parameter | Type | Description |
|---|---|---|
| name | String | Service name. |
| description | String | Description of the service. This parameter is not returned when no service description is registered. |
| Object | Service resource link. | |
| id | String | Service ID. |
| type | String | Service type. |
| enabled | Boolean | Enabling status of the service. |
Example Request
Request for querying service details
GET https://iam.myhuaweicloud.eu/v3/services/{service_id} Example Response
Status code: 200
The request is successful.
{
"service": {
"name": "iam",
"links": {
"next": null,
"previous": null,
"self": "https://iam.myhuaweicloud.eu/v3/services/6cf6e23e00dd49beb13313b024aec598"
},
"id": "6cf6e23e00dd49beb13313b024aec598",
"type": "identity",
"enabled": true
}
} Status Codes
| Status Code | Description |
|---|---|
| 200 | The request is successful. |
| 400 | Invalid parameters. |
| 401 | Authentication failed. |
| 403 | Access denied. |
| 404 | The requested resource cannot be found. |
| 405 | The method specified in the request is not allowed for the requested resource. |
| 413 | The request entity is too large. |
| 501 | The API is not available. |
| 503 | Service unavailable. |
Error Codes
None
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.