FAQ & Troubleshooting
X
Account authentication
X has a concept of staging; the app was moved from development to production.
When trying to authenticate a non-developer X account, users were repeatedly asked to log in even when they already had. The console showed:
Cookie "auth_token" has been rejected for an invalid domain.
The cookie name auth_token is X's session cookie. During the twitter.com → x.com migration, X's pages sometimes try to set auth_token with Domain=.twitter.com while you are on x.com, and the browser rejects it. This warning appears in DevTools but does not actually block OAuth. To confirm it is this: open DevTools → Network, click the request that produced the warning, and check the Set-Cookie header. If the host is x.com, api.x.com or twitter.com, it is X's problem and can be ignored.
Fix: change the domain from twitter.com to x.com in the Social Media Service.
Before:
https://twitter.com/i/oauth2/authorize?
After:
https://x.com/i/oauth2/authorize?
Enabling non-admin Newsmind users to complete account authentication
During training with DW's colleagues, users were unable to authenticate an account after the admin sent them the authentication link. The API Gateway was throwing a 401 for non-admin users.
Fix: remove the permission check on the activation endpoint.
Posting — CreditsDepleted
When posting, users received:
Your enrolled account [1656632801993580548] does not have any credits to fulfill this request.
https://api.twitter.com/2/problems/credits
This is related to the type of billing configured for the developer account. X supports two billing types: Pay Per Use (PPU) and Subscription.
Pay Per Use (PPU) — the default for all new developers since February 6, 2026:
- No monthly subscription. Credits are pre-loaded into the project's billing account and X deducts from that balance as the app makes API calls.
- Per-action pricing (after the April 2026 adjustment): standard post writes ~$0.015, posts containing a URL ~$0.20, general reads ~$0.005, "owned reads" (your own posts, bookmarks, followers) ~$0.001. Reads are capped at 2M/month total.
- When the balance hits zero, every subsequent call returns HTTP 402 with
type: https://api.twitter.com/2/problems/creditsand titleCreditsDepleted. - There is a developer reward: up to 20% of spend comes back as xAI credits.
Subscription tiers (Basic / Pro / Enterprise) — legacy, closed to new sign-ups:
- Basic $200/month, Pro $5,000/month, Enterprise starting around $42,000/month.
- A fixed monthly quota of reads/writes is included for that flat fee. Going over the quota returns a rate-limit error, not a credits-depleted one.
- Existing Basic subscribers are auto-migrated to PPU after June 1, 2026, so the subscription option is effectively sunsetting for non-Enterprise customers.
Further reading:
- Announcing the Launch of X API Pay-Per-Use Pricing — X Developers
- X API Pricing: Pay-Per-Use Credits + Legacy Tiers — Jesus Iniesta
- X (Twitter) API Pricing in 2026: All Tiers — Postproxy
- X (Twitter) API Pricing: Complete Guide for 2026 — Blotato
- How X's API pay-per-use billing signals a new era for software pricing — Technext
- X Revamps Developer API Pricing, Shifts To Pay-Per-Use Model — MediaNama
- Pay-Per-Use app returns CreditsDepleted — X Developers community
- Credits Depleted even though they are filled up — X Developers community