Collection authorization with both X-Auth-Token and X-Auth-Id headers

Is there a way to include multiple headers for API Key authorisation?

This service I’m using requires this:

Use your Client id and API token values to access the API. Pass them via X-Auth-Token and X-Auth-Id headers respectively.

…but the Authorization interface for a Collection interface only allows one key/value pair.

I could add the second header to each request, and use a variable, but …feels wrong.

Am I missing something?


Hey @gabriel-r

Those Headers can be manually added into the Headers section on the request builder. It’s not wrong, it’s just a different way of achieving the same thing. :grin:

The Authorization helper is basically (there’s some other magic happening depending on the type of auth) going to do that anyway :grin:

1 Like