Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.

next
md 44 lines 2.81 KB
Rendered Raw
1 ---
2 type: "reference"
3 title: "Twitter"
4 description: "Public support knowledge for Twitter."
5 category: "auth-config"
6 visibility: "public"
7 timestamp: "2026-07-16T00:00:00Z"
8 tags:
9 - "twitter"
10 ---
11 # Twitter
12
13 ## Twitter/X requires a customer-owned OAuth app
14
15 Composio managed credentials are not available for the Twitter toolkit. Create
16 an app in the X Developer Portal, then create a custom Composio auth config with
17 that app's credentials before connecting an account. This has been required
18 since managed Twitter credentials were removed in February 2026.
19
20 - [Twitter toolkit authentication details](https://docs.composio.dev/toolkits/twitter)
21 - [Managed Twitter credentials removal](https://docs.composio.dev/docs/changelog/2026/02/12)
22
23
24 ## Use the current auth-config callback URI for Twitter OAuth callback mismatch errors
25
26 For Twitter OAuth callback mismatch errors, configure the Twitter/X developer app with the exact callback shown by the current Composio auth-config flow. Do not use the legacy v1 callback from older support guidance.
27
28 ## Twitter/X posts must stay within X's character counting rules
29
30 Twitter/X enforces strict post length limits. For normal posts, keep the content under 280 characters and follow X's official character-counting behavior, since URLs, Unicode, and special characters may be counted by provider-specific rules.
31
32 ## `client-not-enrolled` and `App not linked to project` usually point to Twitter developer app/project setup issues
33
34 These errors usually mean the Twitter/X developer app is not correctly connected to a Twitter developer project, or the OAuth app configuration is stale after X's API model changes. Verify the app is linked to a project, configured according to the Twitter setup guide, and aligned with the current X API requirements. If the connected account is already `EXPIRED`, recreate the connection after fixing the app configuration.
35
36 ## If X v2 API support appears missing, check for an older Twitter toolkit version
37
38 The current Twitter/X toolkit uses v2 endpoints. If a customer sees behavior that looks like older endpoints, check which toolkit version they are using and retry on the latest available version.
39
40 ## Search and other app-only actions use the Application Bearer Token
41
42 Several X actions—including recent/full-archive search and counts, post lookup by IDs, post usage, label-stream, and compliance-job actions—use app-only authentication. They read the `Application Bearer Token` from the Twitter auth config, not the connected user's OAuth access token.
43
44 If user-token actions succeed but these actions return 401, verify that the bearer token comes from the same X Developer App as the OAuth client credentials and that the app's X API plan allows the endpoint. Adding user OAuth scopes does not repair an invalid app bearer token. Reconnect only when the user grant also needs to change.