Signature Generation Rules

Before integrating with the system, you need to apply for a business (AccessKey) and an encryption key (SecretKey). AccessKey and SecretKey are paired.

Signature Algorithm:

a. Take the original string: body=${body}&nonce=${X-Nonce}&secretKey=${SecretKey}&timestamp=${X-Timestamp}&url=${uri} 
Record as signStr

b. Perform MD5 signature on signStr

Signature Example (1): For example, the request parameters are:

header: X-Timestamp=2025-02-17T10:34:55+08:00     X-Nonce=89c8b3d5f2a74e1b     X-AccessKey=mui2W50H1j-OC4xD6PgQag     X-Signature=a1b2c3...d4e5f6

url:    https://api.upgrade.toolsetlink.com/v1/url/upgrade

body:   {"urlKey": "key1","versionCode": 1,"appointVersionCode": 0}

Signature string: signStr:   body={"key": "key1","versionCode": 1,"appointVersionCode": 0}&nonce=abcdef1234567890&secretKey=89c8b3d5f2a74e1b&timestamp=2025-02-17T10:34:55+08:00&url=/v1/url/upgrade

Signature result: MD5(signStr)

Signature Example (2): (GET request, when body is empty) For example, the request parameters are:

header: X-Timestamp=2025-02-17T10:34:55+08:00     X-Nonce=89c8b3d5f2a74e1b     X-AccessKey=89c8b3d5f2a74e1b     X-Signature=a1b2c3...d4e5f6

url:    https://api.upgrade.toolsetlink.com/v1/url/upgrade

body:   {"urlKey": "key1","versionCode": 1,"appointVersionCode": 0}

Signature string: signStr:  nonce=abcdef1234567890&secretKey=89c8b3d5f2a74e1b&timestamp=2025-02-17T10:34:55+08:00&url=/v1/url/upgrade

Signature result: MD5(signStr)