web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / How to view HTTP reque...
Power Automate
Answered

How to view HTTP request code being sent by HTTP Action

(0) ShareShare
ReportReport
Posted on by

I am trying to interface with the USGS elevation point query service API using Automate.

 

I am having difficulty troubleshooting the errors without seeing the HTTP request code being generated. Is there a way to view this information?

 

I have the API request working in Postman and Python; so, I believe my problem is how I am using Automate.

 

Link to the USGS API documentation: https://ned.usgs.gov/epqs/

 

Snip of the HTTP block inputs:

 

 

Capture.PNG

 

Compared to the HTTP code generated through Postman:

[[GET /epqs/pqs.php?x=-120.437001&y=36.701&units=Feet&output=json HTTP/1.1
Host: nationalmap.gov]]

Categories:
I have the same question (0)
  • MJain Profile Picture
    2,450 on at

    Hi @Anonymous ,

     

    I am not sure why it is not working while it works from Postman. I am getting error while I try to hit the same url from flow. Getting Source url cannot be found. Is there any restriction or licensing requirement for us to hit the url

     

    Thanks

  • Community Power Platform Member Profile Picture
    on at

    @ManishJain 

     

    Thank you for giving this a try. You described the same error I receive when running the request from flow.

     

    From everything I've read on the USGS website, there are no licensing requirements/API key or anything like that.

     

    Do you know anything about viewing the outgoing request from flow? I suspect the request is being compiled incorrectly.

  • Verified answer
    JohnAageAnderse Profile Picture
    1,986 on at

    Hello @Anonymous 

     

    I tried it also using an HTTP action and got the error. From the browser it works. Looked into the settings for the action and turned on the option for Suppress workflow headers.

    After doing that, the HTTP action worked and I got the result 🙂

    Kind regards, John

  • Community Power Platform Member Profile Picture
    on at

    @JohnAageAnderse that was it! I appreciate the help.

     

    I suppose it was adding additional metadata headers which caused a problem for the USGS API.

     

    Anyway, thanks again!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 501 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 323 Moderator

#3
abm abm Profile Picture

abm abm 237 Most Valuable Professional

Last 30 days Overall leaderboard