- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-26-2023 03:42 AM
I'm currently using a REST API step that requires a username and API key-based connection and alias. However, my API authentication method relies on a bearer token rather than an API key. I've attempted to obtain the token using the 'Get Connection Info' step and utilize the result in a data pill picker for the REST API connection, but it was unsuccessful. Could you please provide guidance on how to correctly implement the bearer token for authentication instead of the API key?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-27-2023 06:57 AM
Hi,
Use REST Step in flow designer
Create connection and credential aliases
Select connection alias and pass bearer token in Headers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-27-2023 06:57 AM
Hi,
Use REST Step in flow designer
Create connection and credential aliases
Select connection alias and pass bearer token in Headers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-31-2024 07:42 AM
Hi,
How would you configure the connection and credential aliases where the bearer token has to be regenerated every 1 hour?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2024 10:05 AM
Hi @Dewald, if you found the answer, I'll be greatful to you if you share the solution with me, because I have the same doubt here and can't find the solution, Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-19-2024 11:06 PM
Hi @Jordan Corr_a, I build my own flow to take care of this.
The flow works as follow:
- Trigger on a schedule every 59min
- Do the call to get new token
- Save the token
- I currently save this against a custom field: u_token for the integration user I created.
Would have expected this integration functionality to be OOTB, but got some experience building my own things.
Hope this helps