I’m only familiar with the HTTP Retriever node that I used in past projects, but that node is simple and I didn’t need any authorization for those other projects.
Based on these instructions, how do I apply them in KNIME? Perhaps the GetRequest Node or the Java Snippet Node can be of use?
I have marked this as solved, since the query parameters explained above are what I was looking for.
@qqilihq Thank you again. As a side question, do you know if there’s a way I can read .har files with Knime? (if this requires a lengthy answer, I can make a separate forum post)
@qqilihq Hi Philipp, regarding the OAuth Connector Beta Node, I tried using it for my Twitter API. I know this thread is for Facebook, but since you recommended the node here, I’d like to point out that I found the node to not work with Twitter, as you’ve been made known in this forum thread → here which was closed.
Here’s what happened:
I keyed in my API & Secret Keys, and proceeded with the Authorize button. But nothing occurred. (No browser window pops out)
Since I thought this might have something to do with my default Knime configuration just to check it out, I went to the File Menu > Preferences > General > Web Browser, and my default setting was like this:
And still got no results. Just to play around, I randomly choose some of the other services apart from Twitter, but this time with dummy access tokens, and I managed to get the Chrome browser to pop out. I’d appreciate it if you can take a second look at the Twitter issue I just got my v2 access token this week, so in the meantime I’ll have a go at the Twitter API Connector Node.
I keyed in my API & Secret Keys, and proceeded with the Authorize button. But nothing occurred. (No browser window pops out)
Currently some errors are logged to the console*, but might be filtered out if your log level is too high. You can enable DEBUG logging and probably see some helpful output in the console.
If you’d see the DEBUG log, I’d highly suspect that you’ll see something like this along the lines:
response body: <?xml version='1.0' encoding='UTF-8'?><errors><error code="417">Desktop applications only support the oauth_callback value 'oob'</error></errors>
If that’s the case, you’ll need to set up “User authentication set up” in your Twitter project:
The crucial part is to supply the “Callback URI / Redirect URL” which must be exactly as follows (see node documentation):
http://localhost:55931
I’m still collecting plenty of feedback for this node, so please do let me know if that helps!
Best,
Philipp
*) We’ll improve this in the next release to show a proper error dialog as console output usually just gets lost
Okay, I have enabled the User authentication setup as instructed, and I managed to get access via the node now. I’m wondering why does Twitter give me these two additional tokens: Client ID & Client Secret ID right after I set up the authentication, when the only tokens I need are the API key and the API secret key (for the OAuth Beta Node) (and Access token & Access Token Secret for the Twitter API Connector).
Anyway, here’s the screen showed to me once authenticated:
My project doesn’t require me to make POST requests, rather only GET requests. I’m hoping/assuming this “offline.access” scope, whatever that means, will not be troubling me in any way.
I have the ID and the bearer token, but I don’t know how to convert this to the complete URL. The difference between this curl and that of the Facebook’s: