Value for user-agent required to use the API

To continue using the API, a value for user-agent mus be sent from May 1st, 2022.

Posted by Alex on
54 seconds

Actually a value for the user-agent is already sent in most cases. So this change shouldn't affect a lot of our users. But just to be sure, we want to communicate the upcoming change and give you enough time, to check and make changes to your applications.

To break it down a little bit: It's about the user-agent. We expect it in all of your requests from May 1st, 2022. It's not important what you actually set for the user-agent as long as it's present and is not empty. In general, user-agents are used in a form of an identifier for programs or software that is used to access the content. Beside of the name of that program, the user-agent can contain a few more information, e.g. version number. If you use curl to query a domain name on your command line at our API, it'll sent a user-agent like curl/7.81.0 by default. In such cases, you don't have to change anything.

From May 1st, 2022, all requests will receive the HTTP status code 400 (Bad Request), if there is no user-agent sent.

Tags: