This topic describes the common parameters for the Optimization Solver API.
Request parameters
The following common request parameters apply when you call Optimization Solver APIs by sending GET requests.
Name | Type | Required | Example | Description |
Action | String | Yes | StartExecution | Name of the API |
AccessKeyId | String | Yes | LTAI**************** | The ID of the AccessKey. For more information, see Obtain an AccessKey pair. |
Signature | String | Yes | OLeaidS1JvxuMvnyHOwuJ%2BuX5q**** | Your signature. |
SignatureMethod | String | Yes | HMAC-SHA1 | The signature method. Default: HMAC-SHA1. |
SignatureVersion | String | Yes | 1.0 | The version of the signature algorithm. Default: 1.0. |
SignatureNonce | String | Yes | 3ee8c1b8-****-44af-****-4e0ad82fd6cf | A unique random number used to prevent replay attacks. Use a different number for each request. |
Timestamp | String | Yes | 2018-01-01T12:00:00Z | The timestamp of the request. The time must be in UTC and specified in the ISO 8601 standard format: yyyy-MM-ddTHH:mm:ssZ. |
Version | String | Yes | 2021-07-30 | The API version. The format is YYYY-MM-DD. Default: 2021-07-30. |
Format | String | No | JSON | The format of the response. Valid values: JSON and XML. Default: JSON. |
Parameter Examples
https://opt.cn-beijing.aliyuncs.com/?Action=XXXXXX
&Format=JSON
&Version=2021-07-30
&Signature=Pc5W****************************
&SignatureMethod=HMAC-SHA1
&SignatureNonce=15215528852396
&SignatureVersion=1.0
&AccessKeyId=LTAI****************
&Timestamp=2018-01-01T12:00:00Z
…Common response parameters
Name | Type | Description |
RequestId | String | The unique identifier of the request. A request ID is returned regardless of whether the call is successful. |