A client is trying to retrieve info from a 3rd party website. He can log into the website and (with appropriate API key) can access the info he wants manually.
He has written a script that pieces together the string (including API key and various search params) that needs to be sent to the website.
He can copy/paste the string into the browser, and it returns data as expected.
But when he does something like:
request = New HTTP Request( Url( strg ), Method( "GET" ) );
data = request << Send;
(where "strg" is the string containing the description of the request), "data" returns a message saying he is not authorized to make the request, as if he isn't logged into the site.
So... does anyone know if this is an authentication problem with the site? Or perhaps a browser setting that is preventing the access from JSL? (FYI we tried both Edge and Chrome.)
Thanks!
This advice assumes that you needed to log in separately on Chrome and Edge.
Think of JMP as a third browser. The website saw one client log in (Chrome) and could then work well with Chrome. The website saw a second client log in (Edge) and could then work well with Edge. But the website never saw a third client log in (JMP).
So I believe you'll need an HTTP request that logs in, preceding the request where you ask for data.
I've run across situations where the key isn't shown as part of the URL, but via a separate argument. NOAA's Web Services API comes to mind. If you look at the examples, the only thing that appears to be specified is the base URL and the endpoint. No place for a key.
