The apikey doesn’t go in the headers like that. You can put it in the url or in the actual payload or use HTTP Basic Authentication (recommended method)
Thanks for your very quick reply! Yes, I’ve read and re-read that section many times!
It does sort of infer that it goes in the header, doesn’t it? It says for the GET method, you can use apikey or replace it by base64 coded Authorization (I tried that too!).
Then it shows the POST method with base64 coded Authorization in the header! So that is why I am confused.
Anyway, I’ve tried to follow your suggestion. Is this what you meant?
That’s a good sign. It means that you’re authenticated and just need to fill in some extra fields. Add data field to the payload and it should work
If you do want to use HTTP basic authentication there’s a super simple way to do it with the requests library here: Authentication — Requests 2.28.2 documentation
It’ll take care of the encoding for you