Cette page n'est pas encore disponible dans votre langue. Nous nous efforçons d'ajouter d'autres langues. Nous vous remercions de votre compréhension.
API Request Signing Guide
API Request Signing Guide
-
Developer Guide
- Overview
- AK/SK Signing and Authentication Algorithm
- AK/SK Signing and Authentication Guide
- Error Codes
-
FAQs
- How Do I Call APIs in a Subproject?
- Does API Gateway Support Persistent Connections?
- Must the Request Body Be Signed?
- Are Request Header Parameters Required for Signing Requests?
- How Do I Use a Temporary AK/SK to Sign Requests?
- Common Errors Related to IAM Authentication Information
- What Should I Do If "The API does not exist or has not been published in the environment." Is Displayed?
- Change History
On this page
Show all
Help Center/
API Request Signing Guide/
Developer Guide/
AK/SK Signing and Authentication Algorithm/
AK/SK Authentication Process
AK/SK Authentication Process
Updated on 2022-09-08 GMT+08:00
The AK/SK-based authentication process at the client is as follows:
- Construct a standard request.
Assemble the request content according to the rules of API Gateway, ensuring that the client signature is consistent with that in the backend request.
- Create a to-be-signed string using the standard request and other related information.
- Calculate a signature using the AK/SK and to-be-signed string.
- Add the generated signature to an HTTP request as a header or query string.
The following describes the process in detail.
NOTE:
You can follow the instructions provided in this chapter to sign API requests.
You can also call APIs by using the signing SDKs and sample code of common languages described in Signing SDKs and Demo.
Parent topic: AK/SK Signing and Authentication Algorithm
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
