Most common http errors occurring on this API and how to solve them
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 or a NotEnoughCreditsError:
- You don't have enough credits to run the API call.
- You're on a Starter plan and don't have automatic access to our API.
If you need to increase your credit counts, you can do so by upgrading your plan or buying additional credits. Head over to the API dashboard menu in your AppTweak account. Look for the API section of our add-ons. From there, you can either manage your plan or buy additional credits.
If you're on a Starter plan and would like to access our API, you'll need to upgrade to an AppTweak Pro plan or above. To do so, head over to the API dashboard menu in your AppTweak account. Look for the API section of our add-ons and click "Get API." You'll then be able to select a new plan.
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).
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.