I'm trying to do a POST to an API using the HTTP action. I've successfully tested the URI using Postman, it uses only query parameters, no headers or seperate verification (key is also in the parameters).
The HTTP action returns an error: BadRequest - ConnectionFailure, Unable to connect to the remote server.
Being inexperienced in API calls, this is what I thought to try:
Does anyone know how to debug this further? And what could cause the HTTP action to fail while the browser and custom connector succeed with the same URI?
I have copied the Flow several times without changing anything. Now some of these flows consistently work and some consistently don't. My best guess is that each Flow uses its own IP address and some of those are blocked by the receiving API. If anyone can confirm this it would be appreciated.
Yes, I am definitely doing a POST call with parameters. The authentication key is one of the parameters. This is not best practice, but hey, it's not my API 😉
Thanks for replying!
Here's the Flow:
In the meantime I have copied the Flow several times without changing anything. Now some of these flows consistently work and some consistently don't. My best guess is that each Flow uses its own IP address and some of those are blocked by the receiving API. Would you say that the only explanation? Or the most likely reason?
Hi @J-WVanDerLinden ,
The API key that you are using is the cause for this. If this still holds good it will work otherwise it wont and I believe there is nothing stopping based on IP .
I don't think it is possible that the API key is the cause. As I have used the same API key in both Flows and one Flow does work consistently.
I have asked the owner and the host of the API to check incoming connections and whether they're blocked.
Learn how to create your own user groups today!
Check out the new Power Platform Community Connections gallery!
Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.