X (Twitter) OAuth2 — "Something went wrong" on authorization Hey team, Twitter OAuth2 connection via Composio suddenly stopped working. When redirected to Twitter's auth page, I immediately get: "Something went wrong. You weren't able to give access to the App." No changes on my end — it was working before. Setup: - Using Composio's managed OAuth (default credentials, not custom) - Reddit works perfectly with the same flow - Tested on Chrome, logged into X Auth URL generated by Composio: https://twitter.com/i/oauth2/authorize?redirect_uri=https%3A%2F%2Fbackend.composio.dev%2Fapi%2Fv1%2Fauth-apps%2Fadd&response_type=code&scope=dm.write+dm.read+...+offline.access&client_id=Ylk5cUQteFg2d2pvZWt5U0lFZl86MTpjaQ&code_challenge=...&code_challenge_method=S256 URL params all look correct. Tried removing and reconnecting — same result. Questions: - Is the managed X OAuth app currently having issues? - Any changes after the BEARER_TOKEN deprecation (Dec 2025) that might affect this? - Could 20+ scopes be a problem on X Free tier? Thanks! https://cdn.discordapp.com/attachments/1470591074757120050/1470591075432530165/image.png?ex=698bda2a&is=698a88aa&hm=0d684be768377cab6300779cffcc2179650e44d47da877235f6625c592c627ac&

Hey @홍길동, let me check with the team team and get back.

Yeah thanks

https://status.composio.dev/cmlg0tap2016ybi78i4i1vnd2 hey we are having an incident with composio managed x auth

When do you predict that it's going to be solved?

Same issue

we are in touch with support

Same here

unfortunately not, our oauth app has been suspended and we haven’t heard back from support yet we have escalated through our networks

Would there be a way for Composio to prevent incidents like this to happen? Like having official partnerships with integrated platforms

we have with some providers and try to expand that but twitter is notorious for not like their api used after they were bought

Oh okay I see. Hope this can be solved well

unfortunately not, here is a post mortem https://composio.dev/blog/incident-report-february-9-2026

I don't understand why mine works

Hey @홍길동, jumping in to help, could you share the logId of any tool call made via Composio's managed connected account?

I was able to connect to twitter, but the tools didn't work

Hey @홍길동, sorry for the misunderstanding our pricing [page](https://composio.dev/pricing) might've caused you. For tool calls specifically, our pricing models are Composio as a Service, which includes a lot of features such as token refresh handling, tool calls and their logs, and tools and triggers to choose and use from, etc. We do provide managed OAuth apps, and we recommend using them only for development purposes since using your own credentials offers a lot more control over the app and users and configuration freedom. That said, our Twitter app has been suspended by Twitter due to the recent pay-per-use model change, and we had to remove the managed OAuth app ☹️. Let me know if you need any help!

I made 5 tool calls and it cost me 0.83 dollars... Its insanely expensive to use from X. Is there any possibility that composio managed twitter tool calls will be back? Thanks for your support by the way https://cdn.discordapp.com/attachments/1470591074757120050/1473201532634923088/image.png?ex=69955958&is=699407d8&hm=59ea18bfeb708c8ea87b56aa0d0b8518fe19d9b671814acf3969bb7c51cc50a9&

Unfortunately, we don’t currently plan to support managed credentials for Twitter. You can refer to our changelog: https://docs.composio.dev/docs/changelog/2026/02/12 You can keep an eye on our changelog to see if we add managed credentials in the future.