Help needed - HTTP Headers issue

[AMacourek]

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. 

[francbaviello]

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.

[AMacourek]

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,"}

[francbaviello]

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.

[rajeshjanapati]

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?