X
Difficulty: GatedAny X user can connect as soon as you register an app in the X Developer Console, and the docs describe no app review. You must still buy prepaid pay-per-use credits, because new developers get no free tier and calls fail without a balance.
- Your work
- 30–90 min
- Waiting on X
- None
- First user connects
- Today, in about an hour, once you've bought credits
Plan
11 tasksSetupBefore you start
BuildYour app
work 30–90 min · wait noneAny X account, including yours. The docs describe no development mode or test-user list.
LaunchPublic use
work 0–30 min · wait noneAny X user, as long as your credit balance and spending limit allow calls.
Why gated
- Tier
- The docs describe no app review, but you can't use the API at all until you buy credits, and volume past 3M post reads per billing cycle needs an Enterprise plan.
- Using Composio?
- Composio lists Twitter (TWITTER) and X MCP under bring-your-own OAuth apps. Register your own X app, load credits on it, and enter its Client ID and Secret in Composio.twitter
- Your app
- Users see: X's standard authorization screen, showing your app name and the requested scopes.Next: Buy credits, and keep the balance positive.Docs2, 3, 4· medium confidence
- Public use
- Users see: The same authorization screen. The docs mention no unverified-app warning.Docs3· medium confidence
When you get stuck
3
402 CreditsDepleted on every API call
The app's credit balance is zero or negative.
FixBuy credits or turn on auto-recharge in the Developer Console.
"Something went wrong" page on X after authorizing
Usually the redirect URI doesn't match exactly, an invalid scope was requested, or the scopes exceed the app's permission level.
FixCheck that the callback matches exactly, request only documented scopes, and raise the app's permissions if you need write access.
Token exchange fails with invalid_request
The authorization code expires 30 seconds after approval, or the PKCE verifier doesn't match.
FixExchange the code immediately, using the same code_verifier.
Docs1· medium confidence
Not confirmed
3
Does X ever review or restrict OAuth apps before public use?
The docs mention suspension and appeals but no proactive review. The use-case profile's review process isn't documented.
ResolveCheck the Developer Console after you create the app, or ask on devcommunity.x.com.
Is there a limit on the number of users who can authorize an app?
None of the fetched docs mention per-app user caps.
ResolveCheck the X API rate-limit docs and the console.
Is any free access still available?
Third-party reports mention case-by-case free access for public-utility apps, and the official pricing page doesn't mention a free tier.
ResolveContact X developer support.
Sources
9
- 1OAuth 2.0 Authorization Code Flow with PKCEX Developer docs · Official docs · checked 27 Oct 2026
- 2Getting accessX Developer docs · Official docs · checked 27 Oct 2026
- 3PricingX Developer docs · Official docs · checked 27 Oct 2026
- 4Developer appsX Developer docs · Official docs · checked 27 Oct 2026
- 5Supabase X OAuth "Something went wrong" threadAnswer Overflow · Community · not yet checked
- 6Twitter/X authReplit docs · Search results · not yet checked
- 7X API Error Codes DecoderOpenTweet · Search results · not yet checked
- 8Managed auth toolkitsComposio docs · Composio docs · checked 27 Oct 2026
- 9X API pay-per-useGigazine · Search results · not yet checked
Feedback
On the version researched 27 Oct 2026- worked
- 0
- waiting on review
- 0
- stuck
- 0
- wrong
- 0