Notifications
Clear all
Features
5
Posts
4
Users
0
Reactions
3
Views
Topic starter
Hi everyone,
I was recently attempting to retrieve some data from my bank, but they have a rather stringent set of requirements that I must adhere to.
One of these requirements involves sending custom HTTP headers during the OAuth2 API trust setup/linking (consent) process.
I would appreciate it if you would consider adding this functionality.
Here's a sample reference from the bank's requirements:
All AIS Service calls require the following headers:
X-Request-ID: a client generated guid to uniquely identify each call
X-IBM-Client-Id: myapp001.ClientId
Posted : 05/12/2020 3:41 pm
Hello,
if this will help - this feature is also needed for HTTP node / oauth2 integration for Getresponse enterprise version, as it requires custom headers.
Posted : 18/02/2021 9:51 am
Topic starter
Great, thank you! I'll look into that suggestion.
Posted : 18/02/2021 11:01 am
I'd also like to implement this. I have a supplier that requires a random string in the header of all requests, including the OAuth2 request.
Posted : 15/04/2021 2:52 pm
Welcome to the community.
Make sure you upvote it. The more votes, the more chances of being added.
Posted : 15/04/2021 5:23 pm