Twitter

Use this guide to configure Twitter/X authentication, choose the credentials each action needs, and troubleshoot developer-app or toolkit-version errors.

Configure Twitter/X authentication

Choose managed or customer-owned OAuth. Use the current managed OAuth flow for the standard connection. Your own X developer app remains appropriate when you need control over app settings, provider plan, scopes, or branding.

Match the current Composio callback exactly. 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 a legacy v1 callback from older examples.

Publish and search with the correct credentials

Follow X's post-length rules. 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.

Use the Application Bearer Token for app-only actions. 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.

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.

Troubleshoot developer-app and toolkit-version errors

Fix client-not-enrolled and App not linked to project in the X developer app. 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.

Update older toolkit versions for X v2 support. The current Twitter/X toolkit uses v2 endpoints. If you see behavior that looks like older endpoints, check the toolkit version and retry on the latest available version.