Twitter authentication - which tokens?

[Liam]

I can’t authenticate on Twitter. I have read and implemented the guidance here:

https://www.make.com/en/help/apps/marketing/twitter#create-client-credentials-from-your-custom-app

But either I’m doing something wrong or something else is going wrong.

Here are the steps I take:

1. Create a Tweet (v2)
2. Create a connection - if I don’t go to advanced settings, I get this error:

{“message”:“The request failed due to failure of a previous request.”,“code”:“SC424”,“suberrors”:[{“message”:“Status Code Error: 401”,“name”:“RuntimeError”}],“debug”:[[“undefined:”,“response”,401,{“body”:{“{"errors":[{"code":32,"message":"Could not authenticate you."}]}”:“”},“headers”:{“date”:“Fri, 19 May 2023 08:40:03 GMT”,“perf”:“7626143928”,“pragma”:“no-cache”,“server”:“tsa_f”,“status”:“401 Unauthorized”,“expires”:“Tue, 31 Mar 1981 05:00:00 GMT”,“set-cookie”:[“guest_id=v1%3A168448560382189798; Max-Age=34214400; Expires=Tue, 18 Jun 2024 08:40:03 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None”],“content-type”:“application/json; charset=utf-8”,“cache-control”:“no-cache, no-store, must-revalidate, pre-check=0, post-check=0”,“last-modified”:“Fri, 19 May 2023 08:40:03 GMT”,“x-transaction”:“e07b8640b8ad1eb0”,“content-length”:“64”,“x-frame-options”:“SAMEORIGIN”,“www-authenticate”:“OAuth realm="https://api.twitter.com", api_error_code=32”,“x-transaction-id”:“e07b8640b8ad1eb0”,“x-xss-protection”:“0”,“content-disposition”:“attachment; filename=json.json”,“x-content-type-options”:“nosniff”,“x-twitter-response-tags”:“BouncerCompliant”,“strict-transport-security”:“max-age=631138519”,“x-response-time”:“103”,“x-connection-hash”:“fa49a4a7b283d369356b6361ba2a633dea4b7bca332fea272884de456014a08d”,“connection”:“close”}}]]}

If I do go to advanced settings, and put in the keys from my app, from my Twitter Developer Portal, I get similar errors.

Some questions:

1. Which keys from the Portal should I use? The Consumer Keys or the OAuth 2.0 Client ID and Client Secret?

In either case, I get an error though. For example, using the OAuth keys:

{“message”:“The request failed due to failure of a previous request.”,“code”:“SC424”,“suberrors”:[{“message”:“Status Code Error: 401”,“name”:“RuntimeError”}],“debug”:[[“undefined:”,“response”,401,{“body”:{“{"errors":[{"code":32,"message":"Could not authenticate you."}]}”:“”},“headers”:{“date”:“Fri, 19 May 2023 08:43:35 GMT”,“perf”:“7626143928”,“pragma”:“no-cache”,“server”:“tsa_f”,“status”:“401 Unauthorized”,“expires”:“Tue, 31 Mar 1981 05:00:00 GMT”,“set-cookie”:[“guest_id=v1%3A168448581592244161; Max-Age=34214400; Expires=Tue, 18 Jun 2024 08:43:35 GMT; Path=/; Domain=.twitter.com; Secure; SameSite=None”],“content-type”:“application/json; charset=utf-8”,“cache-control”:“no-cache, no-store, must-revalidate, pre-check=0, post-check=0”,“last-modified”:“Fri, 19 May 2023 08:43:35 GMT”,“x-transaction”:“309e37c8858cf4d2”,“content-length”:“64”,“x-frame-options”:“SAMEORIGIN”,“www-authenticate”:“OAuth realm="https://api.twitter.com", api_error_code=32”,“x-transaction-id”:“309e37c8858cf4d2”,“x-xss-protection”:“0”,“content-disposition”:“attachment; filename=json.json”,“x-content-type-options”:“nosniff”,“x-twitter-response-tags”:“BouncerCompliant”,“strict-transport-security”:“max-age=631138519”,“x-response-time”:“104”,“x-connection-hash”:“e8a86bb9b56ef65071cd076c0495f6bb34d01589225cf8480754c6f3f4754ef2”,“connection”:“close”}}]]}

Help would be welcome. I can’t see how I haven’t followed the guidance. Thanks

[juniper_jon]

I’m getting this same issue - did you get this resolved?

[Bruno_T]

Hey there!

The whole Twitter situation is a bit chaotic right now, but I hope I can clarify a bit about the process.

If you’re using the old Twitter modules, please consider upgrading them by clicking on the arrow.

This will also require you to create a new connection to Twitter from within Make with client id and client secret. You can also find a short video here. Please navigate to “Twitter dev” to create a custom app by following the steps above and you’ll be able to use API v2 (our v6 app).

If you have Twitter API v2 Free access, only the Create a Tweet module will be available (with 1500 tweets a month). Additionally, the new Twitter API v2 does not currently support uploading media.

To post Tweets with media, you’ll need to follow the steps here (video here) and connect through our v5 app (Twitter legacy). One of these modules should work:

Please note that we cannot guarantee that Twitter will maintain access to v1.1 and we have no control or responsibility over your OAuth app, so our capability to assist you is limited. The help documentation and video above should contain all the steps necessary to create a working connection, but we cannot guarantee your app will not be shut down by Twitter. It is your responsibility to adhere to their guidelines.

Please also note that in order to use all modules within the updated Twitter app (v6 app, using Twitter API v2), you will need at least the Twitter API v2 Basic access. Free access allows for write only access (1500 tweets a month).

As you’re likely aware at this point, all of these limitations have been implemented by Twitter itself and not by Make. Thank you kindly for your understanding.

[ZX]

With Zapier, it seems that users can use each function of Twitter without creating Basic access themselves. Doesn’t Make open the API to users by getting an enterprise license?

[Matthew_Sabia]

@ZX

T

Welcome to the club.