Making an API Request
This section describes the structure of a REST API, and uses the IAM API for obtaining a user token as an example to demonstrate how to call an API. The obtained token can then be used to authenticate the calling of other APIs.
Request URI
A request URI is in the following format:
{URI-scheme} :// {endpoint} / {resource-path} ? {query-string}
Although a request URI is included in the request header, most programming languages and 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 OCR in the CN North-Beijing4 region is ocr.cn-north-4.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 | Query parameter, which is optional. 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, to obtain an IAM token in the CN North-Beijing4 region, obtain the endpoint of IAM (iam.cn-north-4.myhuaweicloud.com) for this region and the resource-path (/v3/auth/tokens) in the URI of the API used to obtain a user token. Then, construct the URI as follows:
https://iam.cn-north-4.myhuaweicloud.com/v3/auth/tokens
To simplify the URI display in this document, 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 Methods
The HTTP protocol defines the following request methods 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 | Same as GET except that the server must return only the response header. |
| 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 obtain a user token, the request method is POST. The request is as follows:
POST https://iam.cn-north-4.myhuaweicloud.com/v3/auth/tokens Content-Type: application/json
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:
| Header | Description | Mandatory | Example |
|---|---|---|---|
| Content-Type | MIME type of the response body | Yes | application/json |
| Content-Length | Length of the request body, in bytes. | This field is mandatory for POST and PUT requests, but must be left blank for GET requests. | 3495 |
| X-Project-ID | Project ID. This parameter is used to obtain the token for the project. This parameter is mandatory for the request from a DeC or multi-project user. | No | e9993fc787d94b6c886cbaa340f9c0f4 |
| X-Auth-Token | User token | This parameter is mandatory for token-based authentication. | N/A |
| X-Sdk-Date | Time when the request is sent. The time is in YYYYMMDD'T'HHMMSS'Z' format. The value is the current Greenwich Mean Time (GMT) of the system. | This field is mandatory for AK/SK-based authentication. | 20150907T101459Z |
| Authorization | Signature authentication information The value can be obtained from the request signing result. | This parameter is mandatory for AK/SK-based authentication. | SDK-HMAC-SHA256 Credential=ZIRRKMTWPTQFQI1WKNKB/20150907//ec2/sdk_request, SignedHeaders=content-type;host;x-sdk-date, Signature=55741b610f3c9fa3ae40b5a8021ebf7ebc2a28a603fc62d25cb3bfe6608e1994 |
| Host | Server domain name and port number of the resource being requested. The value can be obtained from the URL of the service API. The value is hostname[:port]. If the port number is not specified, the default port is used. The default port number for https is 443. | This field is mandatory for AK/SK-based authentication. | code.test.com or code.test.com:443 |
In addition to supporting token-based authentication, public cloud 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 details, see AK/SK-based Authentication.
The API used to obtain a user token does not require authentication. Therefore, this API only requires adding the Content-Type field. An example of such requests is as follows:
POST https://iam.cn-north-4.myhuaweicloud.com/v3/auth/tokens Content-Type: application/json
Request Body
The body of a request is often sent in a structured format as specified in the Content-Type header field. The request body transfers all content except the request header.
The request body varies depending on APIs. Some APIs do not require the request body, for example, the APIs requested using the GET and DELETE methods.
In case of the API for obtaining a user token, obtain the request parameters and parameter description in the API request. The following provides an example request with a body included. Replace username, domainname, ******** (login password), and xxxxxxxx (project name) with the actual values and obtain the token specified for the project. For example, if the project name is set to cn-north-4, the obtained token applies to the services in cn-north-4. For details about how to obtain a username, domainname, and project name, see Obtaining the Username, User ID, Project Name, and Project ID.
The scope parameter specifies where a token will take effect. You can set scope to an account or a project under an account. In the following example, the token takes effect only for the resources in a specified project. For more information about this API, see Obtaining a User Token.
POST https://iam.cn-north-4.myhuaweicloud.com/v3/auth/tokens
Content-Type: application/json
{
"auth": {
"identity": {
"methods": [
"password"
],
"password": {
"user": {
"name": "username", //Replace the value with the actual username.
"password": "********", //Replace the value with the actual password.
"domain": {
"name": "domainname" //Replace the value with the actual account name.
}
}
}
},
"scope": {
"project": {
"name": "xxxxxxxx" //Replace xxxxxxxx with the actual project name. For example, cn-north-4.
}
}
}
} If all data required for the API request is available, you can send the request to call the API through curl, Postman, or coding. In the response to the API used to obtain a user token, x-subject-token is the desired user token. You can use this token to authenticate the calling of other APIs.
Last Article: Subscribing to OCR
Next Article: Authentication
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.