Skip to main content
This document details the basic information of this API service, availability assurance mechanisms, exception handling specifications, and related notes to help developers understand service boundaries, avoid call risks, and efficiently handle various issues during API calls.

​
I. Service Overview

This API is designed to meet developers’ resource generation, data query, and other business needs. All interfaces return data in JSON format, following unified exception handling specifications to ensure API call consistency and ease of use. Service Core Positioning: Provide efficient and stable API services for developers, supporting rapid integration with various business scenarios, while providing comprehensive problem troubleshooting mechanisms to reduce development and debugging costs.

​
II. Availability Assurance

To ensure stable service operation and improve API call success rates, we establish availability assurance mechanisms from multiple dimensions to ensure long-term stable and efficient service delivery. This API service operates 24/7 continuously throughout the year without interruption, providing service without rest to guarantee business continuity for developers. Exception Notes: If service upgrades, maintenance, or emergency issue handling is required, we will notify developers at least 24 hours in advance through official notification channels (such as developer console announcements, email) to minimize impact on developer businesses. Emergency issues will be prioritized for processing and service recovery.

​
III. Exception Handling Specifications

Various exceptions may occur during API calls. Developers can quickly locate problems based on status codes and return messages and handle them according to the following specifications to improve problem resolution efficiency.

​
3.1 Status Code Handling Logic

  • Status Code 400-499 (Client Error): Prioritize checking client request parameters, request method, token validity, and permissions. No need to contact the server. Common scenarios include missing parameters, format errors, token expiration, etc. Adjust the request according to the returned message field and call again.
  • Status Code 500-599 (Server Error): Server exception. Please retry 1-2 times (interval 1-3 seconds). If still fails, contact technical support.

​
3.2 API Call Failure Retry Suggestions

  • Client Error (400-499): No need to retry. First correct request parameters, permissions, and other issues, then call again.
  • Server Error (500-599): Can retry 1-2 times with 1-3 second intervals. If still fails, stop retrying and contact technical support.

​
IV. Technical Support Channels

When encountering service exceptions, API call failures, and unable to troubleshoot independently, please contact technical support. We will respond and handle within 1 business day.
Last modified on March 12, 2026