Yes. Please follow the registration instructions on the console, and after binding with the business representative, contact them. The business representative will provide you with a free trial.
2. Why do requests sometimes return an error "Time out"?#
To prevent abnormal requests or attacks from affecting overall service, we have imposed restrictions on API requests. By default, we limit requests to a maximum of 800 times per minute. If you require a higher frequency, please contact the business representative. For detailed rules, see [API Guide - HTTP Notes].
3. Can the interface be directly applied to the front-end page?#
No. To ensure your data security, please do not apply the interface directly to the front-end page, as this may expose your secret keys. Please first pull the data to your own server and then apply it to the front-end.
List API call:For the first fetch, loop through the full data based on the input parameter id (the first call has the input parameter id set to empty by default, and subsequent input parameter id is the maximum id from the previous returned data + 1). Determine if total=0 or results are empty; this indicates that the full data retrieval has ended (record the maximum update time updated_at from the full data). After the full data retrieval ends, proceed with incremental updates. For incremental updates, loop through the changed data based on the input parameter time (the first call has the input parameter time set to the maximum update time recorded in step 2 + 1, and similarly, subsequent input parameter time is the maximum update time from the previous returned data + 1). If total=0 or results are empty, the incremental update ends (record the maximum update time updated_at). Maintain incremental updates (every 1 minute/once).
5. When querying with the incremental update time parameter, what should be done if the total number of returned data exceeds the limit?#
When using time queries, because there may be multiple data entries with the same update time, and data with the same update time is returned synchronously, the number of returns from the interface is within the range of the limit; the limit is mainly used for id queries since ids are unique, so the maximum return count is the limit; for time queries, the default limit is sufficient, and no additional settings are needed.
6. After setting the IP whitelist and API authorization, why do requests still indicate that the IP is restricted or the API is unauthorized?#
We have set a time mechanism for the IP whitelist and API permissions. The client’s configured IP address or the API permissions granted by the business representative take effect after one minute.
Yes. Our data supports multi-language output, allowing you to freely choose mainstream languages such as Chinese and English, and output the corresponding language content. This supports your global data requirements.
8. Is it cumbersome to repeatedly fill in the parameters app_id and app_secret in the headers when testing with online documentation?#
There is no need to fill in multiple times; the document sets the headers parameters: app_id and app_secret as variables, and you only need to fill them in the first call. Note that you will need to fill them in again after clearing the web cache.
9. Why does it still return an error "Time out" even if the maximum request count per minute is not reached?#
Each of our interfaces also has its own request frequency. To ensure the stability of data requests, we have set a maximum request count for each interface. For details, see [FAQ - Maximum Request Frequency Limit].
Yes. We offer customized enterprise packages that can be tailored based on data volume, request requirements, timeliness, and other dimensions. Feel free to contact our business team through the official website for further discussions. If you need further refinement of industry scenario cases or technical access documents, please contact the business team for assistance.
