Source URL of HTTP call in Power Automate

[LimeLeaf]

Dear community,

where do I find the source URL an API call is send from out of power automate?
Our API endpoint provider wants to know from where we are calling his API. Because of this we need the "source" URL from where Power Automate executes it's calls against his API.

We are calling an REST API from Power Automate with a HTTP request:

Can anyone help? Where can we find this information? 

Kind regards,
LimeLeaf

[Expiscornovus]

Hi @LimeLeaf,

I do not know if it helps, but Microsoft has published a list of outbound ip addresses:

https://docs.microsoft.com/en-us/connectors/common/outbound-ip-addresses#power-platform

[LimeLeaf]

Thanks for the quick reply!

I also found this link (https://docs.microsoft.com/en-us/connectors/common/outbound-ip-addresses#power-platform), but I was not sure if those are the right IPs. I was somehow expecting some URLs containing our Tenant Name and some kind of explanation how the URL is created with our individual Tenant instead of IPs.

But if this is the solution we are already fine. 🙂 
 

[Expiscornovus]

Hi @LimeLeaf,

I think the url depends on the region and the host executing the requests. But you can probably still check other stuff in the Headers. Maybe the user-agent and the host properties?

Below is an example incoming request in my dev tenant (UK region).

[LimeLeaf]

Hi @Expiscornovus,

thanks for reply. 

I checked the input and output JSON but there is no information about the source where the HTTP call in the cloud is started from. 

As you mentioned I also think that there is somehow a combination of tenant, region etc. that somehow defines the "source" url.  But what is the correct format, how can I test it...

Or are these IP addresses mentioned earlier the right answer to my question!?... 🙂

*confused*

[Expiscornovus · Accepted solution]

Hi @LimeLeaf,

I was checking the Headers on the receiving side of things not where it was sent from. Sorry that I made it a bit confusing. The ip address range could still be a valid approach. I was just looking for a nicer way of identifying the requests 😁

Btw for my test I was using a HTTP action from flow A to send a POST request to flow B. Flow B has a when a HTTP is received trigger action (to simulate the API of the API endpoint provider). In the headers of that trigger action I can see these details.

Hopefully that clarifies things.

[LimeLeaf]

Hi @Expiscornovus,

uhh ya I don't get this. Thanks for the explanation :).

I will try this and hope that it will satisfy the needs of our API provider. Otherwise I will forward the MS outbound table to him as mentioned here earlier.

Thanks for your help!