Get X users by usernames · Twitter / X API
Batch-resolve up to 100 X accounts from a comma-separated list of @handles in a single call, returning one profile object per username. Useful for converting a list of handles into user IDs and profile data in one request.
Using ChatGPT, Claude Code or another client? See the setup steps
curl https://api.unifapi.com/x/users/by?usernames= \ -H "Authorization: Bearer $UNIFAPI_KEY"
Parameters
- expansionsquery
- tweet.fieldsquery
- user.fieldsquery
- media.fieldsquery
- place.fieldsquery
- poll.fieldsquery
- usernamesqueryrequired
- Comma-separated usernames.
This operation is part of the Twitter / X API in the social platforms category. It uses the same Bearer token, request tracing, error model, and billing envelope as every UnifAPI endpoint, so agents can switch between platforms without custom per-vendor glue code.
Use it when a workflow needs Twitter / X public data alongside other social networks, but should still keep one API key, one account balance, and one predictable JSON contract.
Common agent workflows
- Resolve a public Twitter / X identity into structured profile metadata for enrichment agents.
- Refresh creator, company, or account snapshots without managing source-specific response shapes.
- Give an AI agent a stable Twitter / X data source without building a per-platform integration.
- Normalize Twitter / X responses into the same UnifAPI envelope used across the catalog.
Unified envelope, platform-native fields
- Lookup responses return one canonical object in `data` with stable identifiers, source URLs where available, and platform-specific metadata normalized into predictable JSON.
- The `billing.records_charged` field reports the charged billable-record quantity for the successful response.
- A not-found or invalid-input condition uses the unified UnifAPI error shape, so callers do not need special handling for each source platform.
Response status codes
Billing
This operation charges 1 credit per billable record, with a 1 credit ($0.001) operation minimum. Public responses include billing metadata with credits charged, records charged, and remaining workspace balance. Incorrect Credit deductions caused by platform failures can be restored as billing corrections.
Errors and retries
Authentication, validation, rate-limit, not-found, and provider errors use the unified UnifAPI error format. Agents should log `request_id`, retry only retryable failures, and treat invalid API keys, disabled keys, and expired keys as the same public `unauthorized` error type.
Fields on each record in data
A successful Get X users by usernames call returns data as an array; each record carries these fields (12 of 14 shown — the docs list the full schema).
- idstring
- namestring
- usernamestring
- created_atstring
- descriptionstring
- locationstring
- urlstring
- profile_image_urlstring
- profile_banner_urlstring
- protectedboolean
- verifiedboolean
- verified_typestring
Agents & Skills built on Twitter / X
You rarely call Get X users by usernames by hand. These prebuilt agents and skills already read Twitter / X data inside Claude or Codex — start from one of them, or call this endpoint yourself.
Try it free in the browser
Social media handle availability checker
Check a username across every social platform in one shot.
Twitter viewer — see any X profile, post or trend
Free X viewer: paste a handle, post link, hashtag or search. No account, no login to X.
Twitter profile viewer — view any X profile free
See any public X account without logging in: followers, bio, recent posts with views, and engagement rate.
Tweet viewer — view any Twitter / X post free
Paste a Twitter/X post link to read the tweet with its media, quoted post and engagement, no login.
Agents
More Twitter / X operations
Combine endpoints from the same platform, then join the results with other UnifAPI categories without changing authentication or response parsing.
Get verified followers for an X user
Return the subset of an X user's followers that carry a verified badge, as a cursor-paginated list of full profiles. Useful for gauging an account's reach among notable or paying accounts.
Get X user by username
Look up an X (Twitter) account by its @handle (without the leading @) and return the full public profile, including the numeric user ID — the standard way to get a Twitter user ID from a username before calling the follower, timeline, and relationship endpoints. Useful as the entry point when you only know a username.
Get X users by IDs
Batch-resolve up to 100 X accounts in one call from a comma-separated list of numeric user IDs, returning the same profile fields as the single-user lookup. Useful for hydrating profiles behind a list of IDs without one request per account.
Get X user by ID
Resolve a single X (Twitter) account by its numeric user ID and return the full public profile — handle, display name, bio, follower and following counts, verification status, and profile media. Useful when you already hold a stable user ID and need the current profile.
Get an X user's followers
Return a cursor-paginated followers list for a given X (Twitter) user — every account that follows them, with a full profile object per follower. Useful for audience analysis and mapping who follows a brand, creator, or competitor.
Get follower IDs for an X user
Return only the numeric user IDs of an X user's followers as a cursor-paginated list — a lighter, faster payload than full follower profiles. Useful for large-scale audience snapshots and set comparisons such as follower overlap between two accounts.