xapi-v2-credits-depleted-returns-402-not-401
When X API v2 calls fail due to zero account credits, the response is HTTP 402 (CreditsDepleted), not 401 or 403. This is a valid authentication — the Bearer Token is correctly accepted. Diagnosing 402 as an auth failure is a false alarm; the fix is purchasing credits on the X Developer Portal dashboard, not rotating the token.
Related
- x-api-402-credits-depleted-not-auth-failure
- xai-console-vs-x-developer-portal-are-completely-different
- xint-health-shows-red-in-phase1-expected-not-error
- xint-credential-phasing-model-three-tiers
- xint-oauth-callback-port-mismatch-8477-vs-3333
- x-developer-portal-free-tier-only-7day-search
- x-api-v2-402-creditsdepleted-confirms-valid-credentials
- x-api-v2-402-credits-depleted-is-not-auth-failure