Troubleshooting

We had security concerns with your request and could not process it.
Please refer to our troubleshooting section for more information and steps on how to resolve it. If you keep having issues, please let us know at [email protected]

If you’ve received an error message declaring that your request was blocked due to security concerns, please don’t panic.
We know how mission critical our platform is for your business. Therefore we have some strict security controls in place checking all incoming requests.

We actively monitor errors and try to mitigate any false positives as quickly as we can.
Please check if the error might be related to one of the following common pitfalls and get in touch with us at [[email protected]] ([email protected]) if you need further assistance.

Accept header missing

You might have wondered about the special Accept header we’re using already. We try to avoid doing any breaking changes for our API’s but sometimes we simply need to rebuild specific handlers.
Therefore we’ve introduced a versioning schema using the Accept header. If you’re not providing the header we might not be able to correctly process your request and consequently it’s getting blocked.

Content-Type header missing for POST/PATCH requests

If you try to create or update a resource, our API expects the content to be in JSON format. Therefore please make sure to submit the Content-Type: application/json header with your request, otherwise we’re not able to properly parse and inspect it.

Invalid / malformed JSON for POST/PATCH requests

If you try to create or update a resource, our API expects the content to be in JSON format. Therefore please make sure the JSON you’re submitting is valid eg. by using the linter of your favourite IDE.

HTTP status code 429

You got rate-limited. In order to protect our platform we’ve set up a global rate-limit of 10RPS per user. If you think that you need a higher rate, please get in touch with us at [email protected].