For reference, xh also contains this problem, but doesn’t attempt to make the request: $ xh POST httpie. Custom HTTP method, HTTP headers and JSON data: http PUT pie.dev/put X-API-Token:123 nameJohn Submitting forms: http -f POST pie.dev/post helloWorld See the request that is being sent using one of the output options: http -v pie. I think it’s reasonable that nested JSON object specification on the CLI should take precedence over the intent to specify an http header, since the latter would be illegal and not accepted by many HTTP servers. headers Set a custom Host header to work around missing DNS records: http localhost:8000 Host: Simple JSON example: http PUT name. An EdgeGrid Authentication wrapper around cURL that lets you make API calls from the command line. HTTPie A command-line alternative to the cURL utility is HTTPie.4. Session functionality is convenient when you pass API tokens in headers or as part of a request URL. Use the session functionality, so you don’t repeat your authentication. While the server must receive credentials fresh each time, HTTPie can store them to send on your behalf. I’m expecting http POST httpie.io/hello foo=foobar -print=HB and http POST httpie.io/hello foo:='' -print=HB In this case, you set the ' Accept ' header to be ' application. As an API client, HTTPie must abide by the API server’s rules. The Nested JSON CLI syntax allows me to construct a request body without having to type out the raw JSON (loving it), but it seems to collide with how arguments can be interpreted as headers.

Httpie add header