Answered

How to view HTTP request code being sent by HTTP Action

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

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:

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:

Using flows

I have the same question (0)

All responses (4)

Answers (1)

MJain 2,450 on at

Like (0)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@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.

Was this reply helpful? Yes No
Verified answer

JohnAageAnderse 1,986 on at

Like (1)

Report
Copy link

Link copied!

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

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@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!

Was this reply helpful? Yes No