To send a Resource Management API request, you must send an HTTPS GET request to the Resource Management endpoint. You must add the request parameters that correspond to the API operation being called. After you call the API operation, the system returns a response. The request and response are encoded in UTF-8.

Request syntax

Resource Management API operations use the RPC protocol. You can call Resource Management API operations by sending HTTPS GET requests.

The request syntax is as follows:
https://Endpoint/?Action=xx&Parameters
where:
  • Endpoint
    • The endpoint of the Resource Directory API varies based on the API version.
      • For more information about the endpoint of the API of the 2022-04-19 version, see Endpoints.
      • The endpoint of the API of the 2020-03-31 version is resourcemanager.aliyuncs.com
    • The endpoint of the Resource Group API is resourcemanager.aliyuncs.com.
    • For more information about the endpoint of the Tag API, see Endpoints.
    • You can call the DescribeRegions operation to obtain the endpoint of the Resource Sharing API.
    • For more information about the endpoint of the Resource Center API, see Endpoints.
  • Action

    The name of the operation being performed. For example, to create a resource account, you must set the Action parameter to CreateResourceAccount.

  • Parameters

    The request parameters for the operation. Separate multiple parameters with ampersands (&).

    Request parameters include both common parameters and operation-specific parameters. Common parameters include information such as the API version number and authentication information. For more information, see Common parameters.

The following example demonstrates how to call the CreateResourceAccount operation to create a resource account:
Note The sample request is formatted to improve readability.
https://resourcemanager.aliyuncs.com/?Action=CreateResourceAccount
&DisplayName=test
&SignatureVersion=1.0
&Format=JSON
&Timestamp=2020-03-31T12:00:00Z
&AccessKeyId=testid
&SignatureMethod=HMAC-SHA1
&Version=2020-03-31
&SignatureNonce=6a6e0ca6-4557-11e5-86a2-b8e8563d****
&Signature=xxxx%xxxx%3D