Account Info API

GET account/me returns the account tied to the calling API key: email, account holder name, credits_remaining and credits_used (both in USD), total_requests served, and the account's created_at timestamp. It takes no parameters, costs 0 credits, and is not metered, making it safe to call as often as needed to check balance or trigger low-credit alerts.

curl -X GET "https://example.com/account/me"

{  "email": "you@example.com",  "name": "Your Name",  "credits_remaining": 946.4048,  "credits_used": 454.1516,  "total_requests": 622007,  "created_at": "2026-01-14T09:22:31.000Z"}

{  "error": "bad_request",  "message": "Missing or malformed parameter. Fix the request before retrying."}

{  "error": "unauthorized",  "message": "The API key is missing, malformed, or revoked. Check the Authorization header."}

{  "error": "not_found",  "message": "The resource does not exist, for example a deleted tweet or a private account."}

{  "error": "rate_limited",  "message": "Too many requests. Back off and retry with exponential backoff."}

{  "error": "server_error",  "message": "Something failed on our side. Retry with backoff; if it persists, contact support."}

Pricing

When to use

Call GET account/me when you need to check remaining credit balance or usage totals for the API key in use, for example before running a large batch job or to power a balance display in your own dashboard. Use it instead of tracking spend locally, since it reads the authoritative balance directly from the account behind the key.

Notes

• Served from the API root: https://api.twitterapis.com/account/me. It is NOT under /twitter, and /twitter/account/me returns 404.
• Free. This endpoint is not metered and does not consume credits.
• Rate limited to 30 requests per minute per API key. Exceeding it returns 429.
• Both Authorization: Bearer <key> and x-api-key: <key> are accepted.
• This is the BILLING account behind the API key, not the X account your writes post as. To confirm which X account a registered session acts as (resolved username and twitter_user_id, session status, whether your own proxy is in use), call GET customer/session/status. It is free and never returns cookies.

Related endpoints

• Payment History: Every credit top-up on your account, newest first, with amount, credits added, and status.
• Send Feedback: File a bug, idea or missing-capability report from the tool you are using, typically drafted by your AI agent and sent after you review it.
• List Feedback: Page through every feedback report your account has filed, newest first.
• Register Session: Register your auth_token and ct0 cookies once so every write and private read acts as your account, or pass them per call as x-auth-token / x-ct0 headers.

FAQ

Does account/me tell me which X account my posts go out as?

No. account/me describes the billing account behind the API key: email, credits, usage. The X identity comes from the session you registered with customer/session: GET customer/session/status returns the resolved username and twitter_user_id, the session status, and the egress tier, without exposing auth_token or ct0. Call it before a write when the acting account matters.

Does calling account/me consume credits or count against my usage?

No. The endpoint has a cost of 0 and is explicitly not metered, so you can poll it on every request cycle to check your balance without affecting credits_used or total_requests.

How do I show a live credit balance in my own dashboard?

Call GET account/me and read credits_remaining directly; it is already expressed in USD, the same unit as credits_used, so you can compute a percentage-consumed figure by dividing credits_used by credits_used plus credits_remaining without any extra lookups.