El contenido no se encuentra disponible en el idioma seleccionado. Estamos trabajando continuamente para agregar más idiomas. Gracias por su apoyo.
-
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 APIG 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 App Authentication Information Is Incorrect?
- What Should I Do If "The API does not exist or has not been published in the environment." Is Displayed?
- General Reference
Show all
Copied.
Overview
This document describes how to call cloud service APIs that have been registered with API Gateway, through AK/SK authentication. It explains the signing process and implementation logic, and provides signature SDKs and invocation examples of different programming languages, such as Java, Go, Python, and C.
- For the authentication of certain cloud service APIs that are not registered with API Gateway, see the API Reference of the corresponding service.
- The API Reference contains a section named "Calling APIs" that describes API authentication methods.
- The SDK of each programming language is packaged in the sample code and can be obtained separately. You can integrate the SDK into your application by referring to the API calling example.
- If you cannot find any signing example of the programming language you use in this document, please sign requests by referring to AK/SK Authentication.
- Alternatively, you can call APIs using a token. For details, see "Authentication" in the API reference of each cloud service.
- AK/SK authentication supports API requests with a body less than or equal to 12 MB. For API requests with a larger body, token authentication is recommended.
- For the APIs provided by a cloud service, see the API Reference of the cloud service.
- The local time on the client must be synchronized with the clock server to avoid a large offset in the value of the X-Sdk-Date request header.
API Gateway checks the time format and compares the time in the header with the time when API Gateway receives the request. If the time difference exceeds 15 minutes, API Gateway will reject the request.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
