Yes. Please follow the console registration instructions first, bind with our business team, and then contact them. The business team will provide you with free trial access.
2. Why do I sometimes get a "Time out" error when making requests?#
To prevent abnormal requests or attacks from affecting the overall service, we have implemented request limits on our interfaces. By default, we limit a maximum of 800 requests per minute. If you require a higher request frequency, please contact our business team. For detailed rules, see [API Guide - HTTP Precautions].
3. Can the interface be directly applied to the front-end page?#
No. To protect your data security, please do not apply the interface directly to the front-end page, as this can easily expose your API keys. Please retrieve the data to your own server first, and then apply it to the front-end.
4. How should I proceed with data integration for the first time?#
List interface invocation: First acquisition: Loop through to obtain full data based on the input parameter id (the id parameter defaults to empty on the first call, and on subsequent calls it is the maximum id + 1 from the previous returned data). Check if total=0 or results is empty; when true, full data acquisition is complete (record the maximum updated_at from the full dataset). After full data acquisition is complete, proceed with incremental updates. Incremental update: Loop through to obtain changed data based on the input parameter time (on the first call, time is the maximum updated_at + 1 recorded in step 2; on subsequent calls, time is the maximum updated_at + 1 from the previous returned data). When total=0 or results is empty, incremental update is complete (record the maximum updated_at). Continue with incremental updates (once per minute).
5. When querying with the time input parameter for incremental updates, the returned total data count exceeds the limit restriction. How should this be configured?#
When using time query, because multiple data points may share the same update time and data with the same update time are returned synchronously, the interface returns data within the range of the limit restriction; limit is primarily used for id queries because id is unique, so the maximum returned count equals the limit; for time queries, the default limit is sufficient and no additional configuration is needed.
6. After IP whitelist configuration and interface authorization, why do requests still show IP restricted or interface unauthorized errors?#
IP whitelist and interface permissions have an activation delay mechanism. After customers configure IP addresses or the business team grants interface permissions, they take effect within one minute.
7. We need data in Vietnamese and Indonesian. Is this supported?#
Yes. Our data applies multi-language output, allowing you to freely choose from mainstream languages such as Chinese and English, and output the corresponding language content. This supports your global data requirements.
8. When testing using online documentation, is it cumbersome to repeatedly fill in the Headers parameters: app_id and app_secret?#
No need to fill them in multiple times. Set the Headers parameters: app_id and app_secret as variables in the documentation; you only need to fill them in on the first call. Please note that after clearing your web browser cache, you will need to fill them in again.
9. Why do I get a "Time out" error even though I haven't reached the maximum request count per minute?#
Each interface has its own request frequency limit. To ensure stable data requests, we have set a maximum request count for each interface. For details, see [FAQ - Interface Maximum Rate Limit].
Yes. We offer customized enterprise packages that support tailored solutions based on data volume, request requirements, timeliness, and other dimensions. We welcome you to contact our business team through our official website for detailed discussion.If you need further detailed industry scenario cases or technical integration documentation, please contact our business team for assistance.
