This message was deleted.

In case others meet same issue. The APIs requires content-type header to be set to application/json even though the curl request samples in API docs do not have it specified think panic

Hi Jesper, thanks for letting us know about this. I'll make sure we update the documentation accordingly. Sorry for the trouble!

It would be nice if the endpoints could return a message regarding wrong/missing content type instead of payload validation error. My guess is that since content type was wrong it instead silently treated it as an empty payload

I'm always in favor of better warnings / errors. Thank you for drawing this to our attention!