Changes in API Usage – Implemention

Changes in API Usage – Implemention

As of 12 February, you’ll only be able to access our API with a valid API key and user agent via HTTPS. We announced this in December.

To find out whether your client is compatible, you can already send your x-api-key test header when doing a request.

Test without header:

curl -v ‘’

Test with header:

curl -H ‘X-Api-Key-Test: yes’ ‘’

What you need to do:

  • Send requests via HTTPS so that they are encrypted in future
  • Set a user agent header containing information about your domain
  • Submit an API key with it – ideally via the authorization header to send it encrypted

Please make sure to get your requests in line with these criteria so that all works well as of 12 February.

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x