Guest Wallets
Guest Wallet API Status & Payment Activation
Check a guest API key’s activation, credit balance, hosted payment status, and access to tweet, profile, follower, and reply reads. See request fields.
- 200
- 401
- 429
GET
Guest Wallet API Status & Payment Activation
Poll this endpoint after the user completes hosted checkout. The guest key can authenticate this status route while the wallet is pending, but it cannot call paid read routes until payment is verified.
Wait at least
Use
poll_after_seconds before polling again. Continue while it is non-null, then stop. Use usable to decide whether paid reads can run. An active wallet can remain usable while a top-up is pending.
Headers
string
required
Send the guest key as
Bearer xq_your_guest_key_here.Response
string
Available guest wallet credits.
string
Always
paid_reads.string
Combined wallet and pending-checkout state:
active, pending, expired, failed, frozen, or closed. A pending top-up can coexist with usable: true.boolean
Whether the key can call eligible paid read routes.
integer | null
2 while payment is pending. Otherwise null.object | null
Latest amount, credits, expiry, purchase ID, checkout URL while pending, and purchase status.
object | null
Direct REST top-up action when the wallet is usable and has no pending checkout.
string
Guest wallet ID.
Interpret the result
Use these fields together:latest_purchase.status describes only the latest purchase. Use the top-level usable field for paid-read access.
- 200 OK
- 401 Unauthenticated
- 429 Rate limited
usable to decide whether the key can call paid reads.
The response sends Cache-Control: no-store, private and never returns the guest key.
Related: Guest wallet guide · Create guest wallet · Top up guest wallet
- 200
- 401
- 429
Guest Wallet API Status & Payment Activation