HTTP Errors

401 errors

If you're getting a 401 error or an UnknownTokenError when using our API, it is probably because you haven't inserted the correct API token.

You should replace the "header" with your personal API token that you can find in your API dashboard in the AppTweak tool. You can copy your personal token from there and paste it into the header field.

403 errors

There can be several reasons why you might be getting a 403 error:

• You don't own the ressource you're trying to access - UserNotAuthForRessourceError
  • If you're trying to access integration data from App Store Connect, Google Play Console, or Google Play Report make sure always provide the correct api-account-id that can be obtained using the endpoint Integrated Accounts. If you update or change an integration, there will be a new api-account-id that will be generated.

• You don't have enough credits to run the API call.

If you need to increase your credit counts, you can do so by upgrading your plan or buying additional credits.

404 errors

A 404 error stands for "not found." This can appear if you haven't copied the URL for the API correctly. If the error persists, don't hesitate to send us a message.

422 errors

A 422 error stands for "unprocessable entity." This signals that our server understands the request, but is unable to process it.

If you're getting a 422 error or a ValidationError, it's probably because you've used invalid input parameters. Common mistakes can be:

• Inserting more parameters than allowed (e.g., inserting multiple countries at once).
• Inserting non-existent parameters (e.g. a non-existent country code).

429 errors

Toomanyrequests error. When you're having a 429 error, it means that you're hitting the number of concurrent requests that is allowed within your plan. If you're on an unlimited API plan, it will depend on the number of threads you're having in your plan. When you're making more parallel API calls than the number of threads you have, you'll get this error.

500 errors

A 500 error or an internal server error means that our API server has crashed, or that something on our end isn't working. If you encounter such an error, you can send us a message with the API request causing the error, and we will do our best to solve the issue as soon as possible.

504 error

Server timeout error. Our server will time out if your request takes more than 60 seconds to load. Try reducing the amount of data you're trying to pull by reducing the date range, reducing the amount of apps or countries that you provide in the query parameters.