Calling an API after getting API key from Sharepoint List

[Jcastro]

Hi,

I have an API I'm calling where the authentication is an API Key. I have to call this API multiple times but each time with a different API key (which i'm getting from a sharepoint list). Has anyone had any luck doing something similar? I've tried setting the API key as a variable and then passing that into the API call, but Flow uses the connection details stored against the connection rather than what i'm trying to pass in. Have also tried creating a connection within the flow but i can't see how to get the API call to use the connection that has just been created.

Starting to think its not possible.

Any help would be appreciated!

[edguerre]

Hi @Jcastro 

Can you post a picture of the flow here? I think you should be able to pass the API key as dynamic content..

[Jcastro]

Hi,

So here's the flow. I've added an additional step to email me the variable which is the API key. The email proves that the variables  are correctly changing but the data i'm getting back from the endpoint is the same and it should be different for each Key. I think it might be using a default API key that's set up against the connection.

Thanks 

[edguerre]

Thanks @Jcastro . Can you send screenshots of the email with different variables +  same output of the HTTP request action?

Should it not output the same data even with a different API key?

[Jcastro]

Hi, here are the screenshots of the flows where you can see the value of the variables are different and the result is the same.

Each Api key should return a different result set. 

Thanks 

 

[edguerre]

@Jcastro 

It seems so, you are absolutely right.

In this scenario, I would collect those two Flow Run IDs (just save the URL of the flow run), open a Support Ticket with Microsoft and share this info please. It's needed to look into the individual flow runs.

[Jcastro]

@edguerre thanks. I've logged a ticket with microsoft, will post the solution\ outcome here after.

Thanks

[Jcastro · Accepted solution]

Hi @edguerre Had a call with Microsoft but they weren't able to spot the issue so were going to get back to me. But in the interim I managed to work it out, was actually an issue with the customer connector. I created a new collection in postman, making sure that the Headers weren't selected and making sure that all the Params were. When I imported the collection, under security i left it as No Authentication and flow then used the variable value rather than any default.

Thanks for your help.