Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: add Twitter managed credentials removal FAQ
Adds FAQ entry about the removal of Composio managed credentials for the Twitter toolkit, with migration steps and a link to the changelog. Updates the rate limit FAQ to reflect the change. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sushmithamallesh committed
Feb 19, 2026 at 21:22 UTC
53c3713b18624eb517b87e4b3e0c6a4ea04510b4
1 file changed
+10
-1
docs/content/toolkits/faq/twitter.md
+10
-1
@@ -1,6 +1,15 @@
1
+## Why are Composio managed credentials no longer available for Twitter?
2
+
3
+As of February 2026, Composio managed credentials for the Twitter toolkit have been removed. You must now bring your own Twitter API credentials. To migrate:
4
+
5
+1. Create a Twitter Developer account and obtain API credentials from the [Twitter Developer Portal](https://developer.x.com/en/portal/dashboard).
6
+2. Set up a custom auth configuration with your credentials in Composio.
7
+
8
+If you were relying on managed credentials, your Twitter integrations will stop working until you configure your own. See the [changelog entry](/docs/changelog/2026/02/12) for full details.
9
+
10
## Why am I getting rate limit or "UsageCapExceeded" errors on Twitter?
11
3
-The default OAuth app is shared across users and has strict rate limits. It works for testing, but for production use your own OAuth app.
12
+Twitter enforces strict rate limits per app. Use your own OAuth app with appropriate rate limit allocations for production workloads.
13
14
## Why can't I access certain Twitter API endpoints?
15