GET https://xquik.com/api/v1/x/users/{id}
GET /x/users/{id} when a workflow needs one profile row. Use it
for CRM enrichment, lead scoring, account monitoring, or support triage.
Store user_id, username, display_name, bio, follower_count,
following_count, verified, verified_type, profile_url,
profile_image_url, created_at, and unavailable_reason. Do not log
the full lookup response.
Profile row
Store
id as user_id plus username, name, description, followers,
following, verified, and verifiedType.Lookup key
Join on the numeric user ID, which does not change. Use username lookup when the
workflow starts from a handle.
Availability
Store
unavailable and unavailableReason when returned. Retries,
support triage, and CRM syncs can then distinguish missing accounts from unavailable
profiles.Next action
Use the returned
id for followers, following, timelines, media, and
DMs. Use it for follow checks and monitor setup.Store a Twitter profile lookup
Keep the numeric X (Twitter) user ID as the stable key. Profile usernames, names, bios, counts, verification, locations, links, and images can change between lookups.Path parameters
Which user endpoint?
User profile
Use
GET /x/users/{id} for one profile row by username or numeric user ID.Search users
Use
GET /x/users/search when the workflow
starts from a name, keyword, or partial handle.Profile timeline
Use
GET /x/users/{id}/tweets for posts from
one profile.Followers
Use
GET /x/users/{id}/followers when the next
step needs audience rows.Follow check
Use
GET /x/followers/check when the
workflow only needs one source-target relationship.Saved exports
Use
Create extraction.
Create saved CSV, JSON, or XLSX jobs. Export followers, following, timelines,
media, or search.Query parameters
Headers
Response
200 OK
400 Invalid user ID
{ "error": "invalid_user_id", "message": "Send a user ID, @username or profile URL, such as x.com/nasa." }
The path names no user. Send a user ID, username or profile URL.401 Unauthenticated
Missing or invalid API key. Check thex-api-key header value.402 Payment required
Account keys get account options. Guest keys get guest top-up only. Anonymous calls receive a direct MPPWWW-Authenticate: Payment challenge plus a guest wallet creation action.
No checkout starts automatically. Confirm any payment action.404 User not found
X shows no profile for the user. It addsreason, which is not_found, or
suspended when X (Twitter) suspended the account. Check the username or choose another
account.502 X API unavailable
The read service returned an error. Retry after a short delay.429 Rate limit exceeded
You exceeded your tier rate limit. Wait for theRetry-After header before retrying.424 Dependency failed
The normalized v1 response contract can return 424 when the read service is unavailable.Next steps. Check Follower to verify follow relationships. Search Tweets to find tweets from this user.
Response examples
- 400
{ "error": "invalid_input", "message": "Invalid input. Check the request body." } - 401
{ "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." } - 402
{ "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." } - 403
{ "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." } - 404
{ "error": "user_not_found", "message": "X user not found. Check the username." } - 424
{ "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." } - 429
{ "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 } - 502
{ "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." } - 503
{ "error": "x_api_unavailable", "message": "Xquik is busy right now. Retry shortly." }