I’ve struggled with the GET Request node because while I can get a JSON table, I cant figure out how to transform the output from the request into rows and columns that are useable. The KNIME example workflow is too simplistic to help. Any ideas on how I can find out how to configure this node so that I could end up with data structured in rows and column, i.e. a csv file?
I’m looking to retrieve data from stockdata.org where I have a subscription to access stock data via their rest api. You can see more information from their documentation page, which I previously referenced. I’ve included a screenshot of the specific endpoint (adjusted intraday) which is the subject of this issue.
Thanks for your reply and willingness to help me on this. I’ve included screenshots of my custom workflow, the KNIME sample workflow and some of the associated customer configurations as well as a .csv output file which represents my end goal for what I’d like the data to look like.
A second related question has come up. The KNIME sample method calls for a parameter table with which to construct GET urls. Do you have a suggestion on how to configure the workflow to construct subsequent GET calls based on an initial table of multiple rows? KNIME Sample -
I’m unable to convert this JSON Path node output to anything but it does seem like the columns I’ve attempted to create yield some sort of string date. JSON to Table does not interact with the output however.
Thanks. I was actually able to achieve the general results I was looking for by changing the JSON path column configurations in the JSON Path node to something like this: $[‘data’][*][‘data’][‘open’]. This unlocked the data for me.
Now the question is do you have a suggestion on repeating the construction of GET request urls from multiple rows of the REST request table and then appending the successive results to a table?
My data provider throttles the data so I have to make multiple requests.