Elevated access for Twitter Search?

[yakito]

Hi! I am trying to use the Twitter node. I was able to connect it successfully, but when I try to execute a search I am getting the following error suggesting I should apply for “Elevated Access”

But when I go to the Twitter doc page, I see that the search endpoint is part of the “Essential Access”
https://developer.twitter.com/en/portal/products/essential

So I am pretty sure I might be doing something wrong.

Any help will be appreciated!
Thanks!

[marcus]

Hi @yakito,
did you follow our Twitter Credentials documentation?

[yakito]

Hello @marcus , thanks for your answer. Yes, I read that, my question was more towards why do we need mandatory Elevated Access when with Essential Access we should be able to perform search querys.

[Jon]

Hey @yakito,

We use the v1.1 API for search and not the newer v2. We do have an internal ticket opened to use v2 but at the moment there has no work that I can see on it.

[yakito]

Oh, that makes sense @Jon thanks for your answer! Will adjust my needs or use the HTTP node instead. Thanks!

[MutedJam]

Hi @yakito, if you decide to go down the HTTP Request node route, you might want to check out the post linked below. It has a basic HTTP Request node as well as a screenshot of the credential set up for Twitter’s OAuth 1.0a:

OAuth2 and Twitter API

Hi @Dadourlou, I haven’t used Twitter’s OAuth2 yet, but could authenticate with OAuth1 without too much trouble. This allowed me to use Twitter’s API v2 as these endpoints support OAuth1 as well: [image] So if your goal is to simply be able to use the HTTP Request node for API v2 requests you might want to try creating “OAuth1 API” credentials in n8n with these values: [image] The values for Consumer Key and Consumer Secret would be provided by Twitter of course. After connecting, v2 API …

[yakito]

thanks a lot for that @MutedJam , helps a lot!