Docs

Web Application Firewall

Call method

Signature mechanism

When calling the interface, you can authenticate in two ways; only after authentication can you initiate the interface call.

AK / SK authentication: encrypt the call request using Access Key ID and Secret Access Key. AK / SK authentication is recommended as it is more secure than Token authentication.

Token authentication: authenticate through a Token in general requests.

AK / SK authentication

AK / SK authentication uses Access Key ID and Secret Access Key to sign requests, adding the signature information to the <Parameter> during the request. To ensure the legitimacy of the requester's identity and that requests are not maliciously tampered with during transmission, the BytePlus signature mechanism requires the requester to perform a hash value calculation on the <Request parameters>, encrypt it, and send it along with the API request to the server. The server will calculate the signature of the received request using the same mechanism and compare it with the signature provided by the requester. If the signature fails verification, the request will be rejected. For details on how to perform signature calculation, please refer to signature methods.

Token authentication

Token authenticatio adds the Token to the request header when calling the API to authenticate the identity and gain permissions to operate the API. The Token can be obtained by calling the AssumeRole interface.

Last updated: 2025.06.30 16:24:58