Hi Ali. You may be able to create a new Developer account and link your main account through the app created on this new account as mentioned in my video.
If your application does not conform to their policies, you’ll not be able to use their API. It’s your responsibility to ensure that it does.
If you need any further assistance on getting your Twitter integration working, please open a support ticket.
I might answer doubts that are relevant to everyone moving forward, but I don’t want this to become a bloated support thread. Thank you all!
Well, it seems like Twitter is cracking down on individuals creating apps to pull tweets because they JUST suspended my app that I made just over a week ago. Rip
still no solution to this?
I regenerated the AP key and API Key Secret according to the video tutorial on twitter connection, but still reported 401 error when creating a new connection. How to solve this problem?
Find a new method:
The Callback URI / Redirect URL of APP INFO must be filled in: https://www.integromat.com/oauth/cb/twitter
so that the application can be authorized to access twitter through API KEY and API Key Secret, and new Connections to be created successfully. But there is also a new problem. After the Connections of Twitter is successfully created, make will report a 403 error. Haven’t found a solution to the problem yet. The following is the content of the error:
The operation failed with an error. [403] You currently have Essential access which includes access to Twitter API v2 endpoints only. If you need access to this endpoint, you’ll need to apply for Elevated access via the Developer Portal. You can learn more here: Getting Started with the Twitter API | Docs | Twitter Developer Platform
Is there any solution?
Thanks for your suggestion to use this for the Callback URI / Redirect URL:
https://www.integromat.com/oauth/cb/twitter
For some reason the Make.com documentation show a slightly different URL with a ‘2’ on the end:
https://www.integromat.com/oauth/cb/twitter2
For me it was the URL without the 2 on the end that worked for authentication.
Did you find a solution for this [403] Error?
I have tried many times, although make and twitter (Legacy) have been connected, but still did not solve the 403 problem
Hello, it seems we cannot post media (images, videos, …) to Twitter with the new v2 API yet
Hi everyone.
I’m not following this thread, so this will likely be my last reply to it.
If you’re facing issues with your Twitter integration or want to post media, please check the solution of this thread: Twitter authentication - which tokens?
Thank you for your understanding!
That solution does not work. Has Make checked the steps?
Still awaiting a fix to this issue.
I also get “Status code error: 403” after making the connection. I used the https://www.integromat.com/oauth/cb/twitter2 Callback URI to make the connection, and that worked in the pop-up window, but then in Make the process didn’t complete, with the 403 error.
Started receiving this error since 19 of july.
Before that the connection worked well.
I’m using “Get a user” connection and called it once per day.
Now it is broken:
“[403] You currently have access to a subset of Twitter API v2 endpoints and limited v1.1 endpoints (e.g. media post, oauth) only. If you need access to this endpoint, you may need a different access level. You can learn more here: https://developer.twitter.com/en/portal/product”
Is there any update from Make on a direct integration with Twitter? So far it seems like the solution was just a workaround, that ended up breaking relatively quickly.
IFTTT works, Zapier works, etc.
Getting a lot of “ * Failed to verify connection 'My Twitter OAuth 2.0 connection'. Status Code Error: 400 “ messages lately. And yes the auth itself is fine.