Response

Updated on 2025-05-15 GMT+08:00

View PDF

Status Code

After sending a request, you will receive a response, including a status code, response header, and response body.

A status code is a group of digits, ranging from 1xx to 5xx. It indicates the status of a request. For more information, see Status Codes.

For example, if status code 200 is returned for calling the API used to obtain the SSH key list (see Obtaining the SSH Key List), the request is successful.

Response Header

Similar to a request, a response also has a header, for example, Content-Type.

Figure 1 shows the response header fields for the API used to obtain a user token. The x-subject-token header field is the desired user token. This token can then be used to authenticate the calling of other APIs.

Figure 1 Header fields of the response to the request for obtaining a user token
Click to enlarge

Response Body

The body of a response is often returned in structured format as specified in the Content-Type header field. The response body transfers content except the response header.

For the API used to obtain a user token, the response body is as follows: The following example is part of the response body for the API used to obtain a user token:

{ 
    "token": { 
        "expires_at": "2019-02-13T06:52:13.855000Z", 
        "methods": [ 
            "password" 
        ], 
        "catalog": [ 
            { 
                "endpoints": [ 
                    { 
                        "region_id": "eu-west-101",
......

If an error occurs during API calling, an error code and the corresponding error message will be displayed. The following shows an error response body:

{ 
    "error_msg": "The format of message is error", 
    "error_code": "AS.0001" 
}

In the response body, error_code is an error code, and error_msg provides information about the error.

Parent topic: Calling APIs

Previous topic: Authentication

Next topic: APIs

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel