Frequently Asked Questions (FAQ)

This section compiles common questions and answers regarding API usage to help users quickly troubleshoot and resolve issues.

1. Does the API support GET requests?

Currently, all data interfaces on the platform use the POST method.

Reasons for using POST include:

Complex query parameter structures

Avoiding URL length limitations

To enhance parameter security and scalability

Please refer to the documentation for specific instructions when making calls.

2. Why does the response return a success status but the `data` field is empty?

When no data is available based on the query conditions:

The API will return a success status code

The data field will be an empty object or an empty array

This is a normal response and is not considered an API error.

3. Is the data returned by the API real-time?

Most APIs return results calculated based on platform data sources and models, which may involve some delay.

For specific data update times and definition specifications, please refer to:

API documentation

Data dictionary and definition specifications section

4. What should I do if the token expires?

When a token expires or becomes invalid:

The API will return an authentication-related error code

You must obtain a new token before making another request

We recommend implementing a unified handling mechanism for authentication failures in your call logic.

5. Are there limits on API call frequency?

Yes, the platform imposes limits on API call frequency and concurrent requests.

Different accounts or plans have different call quotas

Exceeding the rate-limiting threshold will result in a rate-limiting error code

For detailed rules, please refer to the “Rate Limiting and Stability Guidelines” section.

6. Can API data be used for commercial purposes?

The scope of API data usage must comply with the platform’s service agreement and relevant terms.

If the data involves public display, commercial distribution, or secondary processing, please contact the platform in advance for confirmation.

7. Will API fields change in the future?

The platform may add new fields or expand capabilities without affecting existing logic.

Recommendations for API callers:

Avoid strict validation of return fields

Rely only on the field definitions explicitly stated in the documentation

8. Is it normal for the data to differ from the official App Store data?

Platform data is derived from various public sources and model-derived data, so it may differ from the official App Store backend data.

For relevant data definitions and scope of application, please refer to the “Data Dictionary and Definition Guidelines” section.

2. FAQ

Frequently Asked Questions (FAQ)#

1. Does the API support GET requests?#

2. Why does the response return a success status but the data field is empty?#

3. Is the data returned by the API real-time?#

4. What should I do if the token expires?#

5. Are there limits on API call frequency?#

6. Can API data be used for commercial purposes?#

7. Will API fields change in the future?#

8. Is it normal for the data to differ from the official App Store data?#