Thanks. The HTTP Authorization header works ok with REST API but after reading Users, roles and permissions - Authorization and user configuration I was expecting username/secret URL param to work too and I quote…
When connecting Checkmk to other systems it is often desired that specific tasks normally performed using the GUI be automated. Some examples of these are:
…
- Managing hosts with the REST-API
…
To simplify this procedure Checkmk offers the concept of the Automation user. These users are intended exclusively for remote control and don’t permit normal GUI logins. Authorisation is achieved using specific variables in the URL.
Thanks!