> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xquik.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Get users (batch)
> Retrieve multiple user profiles by ID in a single request, up to 100 at a time
For the complete documentation index, see llms.txt.
Requested result counts are upper bounds for paid authenticated calls. When remaining credits cannot cover the full page or ID list, Xquik returns fewer results. If zero paid results are affordable, it returns `402 insufficient_credits`.
**1 credit per user returned** · [All plans](https://xquik.com/#pricing) from \$0.00012/credit
```bash cURL theme={null}
curl "https://xquik.com/api/v1/x/users/batch?ids=44196397,987654321" \
-H "x-api-key: xq_YOUR_KEY_HERE" | jq
```
```javascript Node.js theme={null}
const ids = ["44196397", "987654321"];
const response = await fetch(
`https://xquik.com/api/v1/x/users/batch?ids=${ids.join(",")}`,
{
headers: { "x-api-key": "xq_YOUR_KEY_HERE" },
}
);
const data = await response.json();
const profilesById = new Map(data.users.map((user) => [user.id, user]));
const profileRows = data.users.map((user) => ({
user_id: user.id,
username: user.username,
display_name: user.name,
bio: user.description ?? null,
follower_count: user.followers ?? null,
following_count: user.following ?? null,
verified: user.verified ?? false,
profile_image_url: user.profilePicture ?? null,
}));
const missingIds = ids.filter((id) => !profilesById.has(id));
```
```python Python theme={null}
import requests
ids = ["44196397", "987654321"]
response = requests.get(
"https://xquik.com/api/v1/x/users/batch",
params={"ids": ",".join(ids)},
headers={"x-api-key": "xq_YOUR_KEY_HERE"},
)
data = response.json()
profiles_by_id = {user["id"]: user for user in data["users"]}
profile_rows = [
{
"user_id": user["id"],
"username": user["username"],
"display_name": user["name"],
"bio": user.get("description"),
"follower_count": user.get("followers"),
"following_count": user.get("following"),
"verified": user.get("verified", False),
"profile_image_url": user.get("profilePicture"),
}
for user in data["users"]
]
missing_ids = [user_id for user_id in ids if user_id not in profiles_by_id]
```
The Node.js and Python snippets shape durable profile rows instead of printing
full profile objects. Persist `profileRows` or `profile_rows` and `missingIds`
or `missing_ids` with the original ID list so retries only request missing
profiles.
## Direct batch user handoff
Use `GET /x/users/batch` when a CRM, warehouse, enrichment, lead scoring, or
agent workflow already has numeric X user IDs and needs profile details in one
JSON response. Use [Get User](/api-reference/x/get-user) when you have one ID
or username to resolve.
Store `requested_ids`, `user_id`, `username`, `display_name`, profile metrics,
verification state, `profile_image_url`, `has_next_page`, and `next_cursor`.
Join returned users by `user_id` instead of relying on response order. Send at
most 100 IDs per request. Batch requests always return `has_next_page: false`
and `next_cursor: ""`; zero affordable results return
`402 insufficient_credits`.
Send comma-separated X user IDs in `ids`. Keep the original list as
`requested_ids` for retry and audit rows.
Store each returned `id` as `user_id` with `username`, `name`,
`description`, `followers`, `following`, `verified`, and `verifiedType`.
Compare returned `user_id` values with `requested_ids`. Retry only the
missing IDs or route username-only inputs to Get User first.
Use the single-page batch contract: `has_next_page: false` and
`next_cursor: ""`. Do not treat it as a cursor workflow.
## Which lookup endpoint?
Use [`GET /x/users/{id}`](/api-reference/x/get-user) for one username or one
user ID.
Use `GET /x/users/batch` for up to 100 comma-separated user IDs in one
request.
Use [`GET /x/users/search`](/api-reference/x/search-users) before batch
lookup when the workflow starts from a name, brand, or handle fragment.
Use [`GET /x/tweets/batch`](/api-reference/x/batch-tweets) when the input
list contains tweet IDs instead of user IDs.
Use [`GET /x/users/{id}/followers`](/api-reference/x/followers) or
[`GET /x/users/{id}/following`](/api-reference/x/following) when the job
starts from an account audience.
Use [`Create extraction`](/api-reference/extractions/create) when the source
is a follower, following, timeline, media, or search job instead of an
existing ID list.
## Query parameters
Comma-separated user IDs. Maximum 100 per request.
## Headers
Your API key. Session cookie authentication is also supported.
## Response
Array of user profiles matching the requested IDs.
X user ID.
X username.
Display name.
Profile bio.
Follower count.
Following count.
Verified status.
Profile image URL.
Profile location.
Account creation date (ISO 8601).
Total number of tweets posted. Omitted if unavailable.
Cover/banner image URL. Omitted if unavailable.
Total number of media tweets posted. Omitted if unavailable.
Whether the user accepts direct messages. Omitted if unavailable.
Website URL from profile. Omitted if empty.
Total number of tweets liked. Omitted if unavailable.
Whether the user has custom timelines. Omitted if unavailable.
Whether the user is an X translator. Omitted if unavailable.
Country codes where the account is withheld. Omitted if empty.
Whether the account is flagged as possibly sensitive. Omitted if unavailable.
IDs of pinned tweets. Omitted if none.
Whether the account is marked as automated. Omitted if unavailable.
Username of the account operator if automated. Omitted if not automated.
Whether the account is unavailable. Omitted if available.
Reason the account is unavailable. Omitted if available.
Verification type (e.g. `Business`, `Government`). Omitted if not verified or standard blue check.
Structured profile bio with entity annotations. Omitted if unavailable.
Always `false` for batch requests.
Always empty for batch requests.
```json theme={null}
{
"users": [
{
"id": "44196397",
"username": "elonmusk",
"name": "Elon Musk",
"followers": 200000000,
"verified": true
}
],
"has_next_page": false,
"next_cursor": ""
}
```
```json theme={null}
{ "error": "missing_ids", "message": "ids parameter required" }
```
```json theme={null}
{ "error": "too_many_ids", "message": "Max 100 IDs per request" }
```
```json theme={null}
{ "error": "unauthenticated" }
```
```json theme={null}
{ "error": "no_subscription" }
```
No active subscription or insufficient credits. Possible error values: `no_subscription`, `subscription_inactive`, `no_credits`, `insufficient_credits`.
```json theme={null}
{ "error": "x_api_unavailable" }
```
The read service returned an error. Retry after a short delay.
```json theme={null}
{ "error": "rate_limit_exceeded", "retryAfter": 60 }
```
Your tier rate limit was exceeded. Wait for the `Retry-After` header before retrying.
```json theme={null}
{ "error": "x_api_unavailable" }
```
The normalized v1 response contract can return 424 when the read service is unavailable.
**Related:** [Batch Tweets](/api-reference/x/batch-tweets) · [Get User](/api-reference/x/get-user)