topic Re: Help needed - HTTP Headers issue in Workato Pros Discussion Board

Help needed - HTTP Headers issue

AMacourek — Wed, 04 Feb 2026 14:41:07 GMT

I have an HTTP Connection that I set up that uses headers for authorization.

The problem is that only the first key is being passed with the request.

Re: Help needed - HTTP Headers issue

francbaviello — Wed, 04 Feb 2026 15:46:26 GMT

Hi @AMacourek , you can set the field 'Endpoint has case-sensitive headers?' -> Yes
You setting two fields key in headers: ApiKey and ApiKeyValue.
You need to set in the key ApiKey the value in textbox value and also for the field ApiKeyValue.

Re: Help needed - HTTP Headers issue

AMacourek — Wed, 04 Feb 2026 16:06:34 GMT

Yes, I already did both of these as you can see below. The first value comes in just fine. This works for other implementations just fine - PowerShell, C#, and Postman. But, with Workato, only the first key is being passed. I have a test endpoint that exports headers that are received to verify what is being sent.

Test with Workato:
"headers":"Accept=application/json,Accept-Encoding=gzip,Content-Length=0,Content-Type=application/json,Host=****,Max-Forwards=10,User-Agent=Workato R2928f4e7ac8/Pv1.0.11,Apikey=***,X-ARR-LOG-ID=7dca95dd-950c-455a-90f3-71ea58b23b6b,CLIENT-IP=***:6806,DISGUISED-HOST=****,X-SITE-DEPLOYMENT-ID=****,WAS-DEFAULT-HOSTNAME***....},

Test with Postman:
"headers":"Accept=*/*,Connection=keep-alive,Host=localhost:58276,User-Agent=PostmanRuntime/7.51.1,Accept-Encoding=gzip, deflate, br,Cache-Control=no-cache,ApiKey=***,ApiKeyValue=***,Postman-Token=3e131945-0f1d-4908-89f5-baa51f97f8fa,"}

Re: Help needed - HTTP Headers issue

rajeshjanapati — Wed, 04 Feb 2026 16:11:39 GMT

Hi @AMacourek,

I think it will be the only one header value we need to pass and I guess in the requirement doc they shared, like key and value as 2 headers and then you may have confused.
one more thing, may know which API you are configuring whether it is Workato Platform API or 3rd party application API?

Re: Help needed - HTTP Headers issue

francbaviello — Wed, 04 Feb 2026 16:23:20 GMT

This is likely a limitation and only the first key is considered and is treated as part of the authorization mechanism rather than as request headers. You can put multiple headers directly in the HTTP action request headers or you can use the Connector SDK where you implement the new invocation.

Re: Help needed - HTTP Headers issue

AMacourek — Wed, 04 Feb 2026 16:34:38 GMT

I need both values as they are a key pair. It looks like a custom connector is needed.

Re: Help needed - HTTP Headers issue

AMacourek — Thu, 05 Feb 2026 13:27:02 GMT

I would say that this is a glaring bug in Workato. If you can add multiple headers in the Connection configuration, then each of those headers must be passed. I have tested this several times and only the first header in the list is actually passed.

Re: Help needed - HTTP Headers issue

shivakumara — Thu, 05 Feb 2026 13:33:37 GMT

Hi @AMacourek ,

If possible, could you please share the expected headers/input for the API endpoint? This will help us better understand the requirement and assist you accordingly.

Thanks and Regards,
Shivakumara K A

Re: Help needed - HTTP Headers issue

AMacourek — Thu, 05 Feb 2026 18:41:53 GMT

Like this with Postman:

I created a custom connection and got it to work there.

Re: Help needed - HTTP Headers issue

rajeshjanapati — Fri, 06 Feb 2026 03:13:41 GMT

Try once by passing the values in the HTTP step in the recipe itself ratherthan in connection setup, may be connections configuration in such a way like it won't read multiple APIKey headers at the connection level and use none connection for HTTP. hope you got my point?

Re: Help needed - HTTP Headers issue

shivakumara — Fri, 06 Feb 2026 04:47:34 GMT

Hi @AMacourek ,

Thank you for sharing the reference.

In this case, you can establish the connection using only the basic details, such as the Base URL, and keep the authorization set to “None.”

All the required and relevant details can be passed directly within the recipe.

Thanks and Regards,
Shivakumara K A

Re: Help needed - HTTP Headers issue

gary1 — Fri, 06 Feb 2026 04:58:34 GMT

I did ~~some~~ a ludicrous amount of testing and have some more input:

I confirmed Workato is definitely passing both headers
I don't think "Endpoint has case-sensitive headers?" actually works

Here's how I tested in case this is helpful for anyone else:

I used nifty tool called https://webhook.site/

This site lets you set up an endpoint to call so you can analyze the data and headers you're sending.

I made this connection and tested it:

Here's the receipt of the request. You'll notice the API headers are downcased. I figured this might be part of the UI of site, so I tried several other similar tools (hooklistener.com, usewebhook.com, play.svix.com) and they all have the same shortcoming -- all of these sites either upcase or downcase the headers before presenting it in the UI. Great.

So, after all this, we're at least sure both headers are being passed, but we're still not sure about a couple things:

Is Workato manipulating the header casing?
Does your API actually have case-sensitive headers?

One last thing: I set up a local HTTPS server, called it from Workato and got this:

Apikey: blahblahblah Apikeyvalue: yadayadayada

The plot thickens.

If your API requires case-sensitive headers, you might be hosed. Hopefully someone else has another idea.

@rajeshjanapati @francbaviello @shivakumara

Re: Help needed - HTTP Headers issue

shivakumara — Fri, 06 Feb 2026 06:48:17 GMT

Hi @gary1 ,

Thank you for the detailed explanation.

I have sent the API key and API key value directly via the recipe, as we are unable to verify the headers when they are sent through the connection configuration. From our observation, Workato is not modifying the headers and is sending them exactly as provided.

Please refer to the attached screenshot for reference. However, it appears that the API endpoint itself is transforming the header names (for example, converting them to lowercase).

Official standard:
RFC 7230 / RFC 9110: HTTP header field names are case‑insensitive

So when an API requires case‑sensitive headers, it usually means:

The API is incorrectly implemented
It violates HTTP standards
Many tools may not support it properly

Thanks and Regards,
Shivakumara K A

Re: Help needed - HTTP Headers issue

AMacourek — Fri, 06 Feb 2026 14:50:20 GMT

What really bothers me is that now it works. I created a new connection and added the headers. Thanks for the heads up about webhook.site. I tested that first and then went to the other API. The casing even works fine.