Making an API Request
Scenario
This section describes the structure of a REST API request, and uses the API for creating an IAM user as the administrator as an example to demonstrate how to call an API.
Request URI
A request URI is in the following format:
{URI-scheme} :// {Endpoint} / {resource-path} ? {query-string}
Although a request URI is included in a request header, most programming languages or frameworks require the request URI to be transmitted separately.
|
Parameter |
Description |
|---|---|
|
URI-scheme |
Protocol used to transmit requests. All APIs use HTTPS. |
|
Endpoint |
Domain name or IP address of the server bearing the REST service. The endpoint varies between services in different regions. It can be obtained from Regions and Endpoints. For example, the endpoint of IAM in the CN-Hong Kong region is iam.ap-southeast-1.myhuaweicloud.com. |
|
resource-path |
Access path of an API for performing a specified operation. Obtain the path from the URI of an API. For example, the resource-path of the API used to obtain a user token is /v3/auth/tokens. |
|
query-string |
An optional query parameter. Ensure that a question mark (?) is included before each query parameter that is in the format of "Parameter name=Parameter value". For example, ?limit=10 indicates that a maximum of 10 data records will be displayed. |
For example, if you want to create an IAM user, use the endpoint of any region (such as iam.ap-southeast-1.myhuaweicloud.com of CN-Hong Kong) because IAM is a global service. You can find the resource-path (/v3.0/OS-USER/users) in the URI of the API for creating an IAM user as the administrator. Then, construct the URI as follows:
1
|
https://iam.ap-southeast-1.myhuaweicloud.com/v3.0/OS-USER/users |
To simplify the URI display, each API is provided only with a resource-path and a request method. The URI-scheme of all APIs is HTTPS, and the endpoints of all APIs in the same region are identical.
Request Method
The HTTP protocol defines the following request modes that can be used to send a request to the server:
|
Method |
Description |
|---|---|
|
GET |
Requests the server to return specified resources. |
|
PUT |
Requests the server to update specified resources. |
|
POST |
Requests the server to add resources or perform special operations. |
|
DELETE |
Requests the server to delete specified resources, for example, an object. |
|
HEAD |
Requests the server to return the response header only. |
|
PATCH |
Requests the server to update partial content of a specified resource. If the resource does not exist, a new resource will be created. |
For example, in the case of the API used to create an IAM user as the administrator, the request method is POST. The request is as follows:
POST https://iam.ap-southeast-1.myhuaweicloud.com/v3.0/OS-USER/users
Request Header
You can also add additional header fields to a request, such as the fields required by a specified URI or HTTP method. For example, to request for the authentication information, add Content-Type, which specifies the request body type.
Common request header fields are as follows:
|
Name |
Description |
Mandatory |
Example |
|---|---|---|---|
|
Host |
Requested server information, which can be obtained from the URL of the service API. The value is in the format of hostname:port. If the port number is not specified, the default port number for https(443) is used. |
No Mandatory for AK/SK-based authentication |
code.test.com or code.test.com:443 |
|
Content-Type |
The request body type or format. The default value application/json is recommended. Other values of this field will be provided for specific APIs if any. |
Yes |
application/json |
|
Content-Length |
The length of the request body. The unit is byte. |
No |
3495 |
|
X-Project-Id |
Project ID. Obtain the project ID by following the instructions in Obtaining a Project ID. |
No Mandatory for requests that use AK/SK authentication in the Dedicated Cloud (DeC) scenario or multi-project scenario. |
e9993fc787d94b6c886cbaa340f9c0f4 |
|
X-Auth-Token |
User token The user token is a response to the API used to obtain a user token. This API is the only one that does not require authentication. After the request is processed, the value of X-Subject-Token in the response header is the token value. |
No Mandatory for token authentication. |
The following is part of an example token: MIIPAgYJKoZIhvcNAQcCo...ggg1BBIINPXsidG9rZ |
In addition to token-based authentication, APIs also support authentication using access key ID/secret access key (AK/SK). During AK/SK-based authentication, an SDK is used to sign the request, and the Authorization (signature information) and X-Sdk-Date (time when the request is sent) header fields are automatically added to the request.
For more information, see "AK/SK-based Authentication" in Authentication.
For the API used to create an IAM user as the administrator, if AK/SK authentication is enabled, the request with the header is as follows:
POST https://iam.ap-southeast-1.myhuaweicloud.com/v3.0/OS-USER/users Content-Type: application/json X-Sdk-Date: 20240416T095341Z Authorization: SDK-HMAC-SHA256 Access=****************, SignedHeaders=content-type;host;x-sdk-date, Signature=****************
Request Body (Optional)
The body of a request is often sent in a structured format as specified in Content-Type. The request body transfers content except the request header. If the request body contains Chinese characters, set Content-type to utf-8, for example, Content-Type: application/json; charset=utf-8.
The request body varies depending on APIs. Some APIs do not require the request body, such as the APIs requested using the GET or DELETE method.
For the API used to create an IAM user as the administrator, the required parameter and description are in the request part of the API. An example of such requests is as follows. Use actual values for the bold fields.
- accountid: account ID of the IAM user
- username: IAM username to be created
- email: email address of the IAM user
- **********: password of the IAM user
POST https://iam.ap-southeast-1.myhuaweicloud.com/v3.0/OS-USER/users
Content-Type: application/json
X-Sdk-Date: 20240416T095341Z
Authorization: SDK-HMAC-SHA256 Access=****************, SignedHeaders=content-type;host;x-sdk-date, Signature=****************
{
"user": {
"domain_id": "accountid",
"name": "username",
"password": "**********",
"email": "email",
"description": "IAM User Description"
}
}
If all data required for the API request is available, you can send the request to call the API through curl, Postman, or coding.
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