> ## 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.
# Twitter Profile Search, Lookup & Audience Counts
> Search a Twitter or X profile by username or user ID. Retrieve the bio, follower and following counts, verification status, location, and links. See costs.
For the complete documentation index, see llms.txt.
* Profiles: [Search users](/api-reference/x/search-users) · [Get user](/api-reference/x/twitter-profile-lookup) · [Batch users](/api-reference/x/batch-users)
* Followers: [Followers](/api-reference/x/followers) · [Following](/api-reference/x/following) · [Verified followers](/api-reference/x/verified-followers) · [Followers you know](/api-reference/x/followers-you-know) · [Check follower](/api-reference/x/check-follower)
* Lists: [List members](/api-reference/x/list-members) · [List followers](/api-reference/x/list-followers)
* Communities: [Details](/api-reference/x/community-info) · [Members](/api-reference/x/community-members) · [Moderators](/api-reference/x/community-moderators) · [Timeline](/api-reference/x/community-tweets) · [Keyword search](/api-reference/x/community-search)
**1 credit per call** · [All plans](https://xquik.com/#pricing) from \$0.00012/credit · Direct [MPP](/mpp/machine-payments-protocol): USD 0.00015 per call
See [Read Data Richness](/guides/tweet-profile-api-fields) for every optional
profile field. Xquik omits fields that X does not supply.
```bash cURL theme={null}
curl https://xquik.com/api/v1/x/users/username \
-H "x-api-key: xq_your_api_key_here" | jq
```
```javascript Node.js theme={null}
const username = "username";
const response = await fetch(`https://xquik.com/api/v1/x/users/${username}`, {
headers: { "x-api-key": "xq_your_api_key_here" },
});
const data = await response.json();
const profileRow = {
user_id: data.id,
username: data.username,
display_name: data.name,
bio: data.description ?? null,
follower_count: data.followers ?? null,
following_count: data.following ?? null,
verified: data.verified ?? false,
verified_type: data.verifiedType ?? null,
profile_url: data.url ?? null,
profile_image_url: data.profilePicture ?? null,
created_at: data.createdAt ?? null,
unavailable_reason: data.unavailableReason ?? null,
};
process.stdout.write(`${JSON.stringify(profileRow)}\n`);
```
```python Python theme={null}
import json
import requests
response = requests.get(
"https://xquik.com/api/v1/x/users/username",
headers={"x-api-key": "xq_your_api_key_here"},
)
data = response.json()
profile_row = {
"user_id": data["id"],
"username": data["username"],
"display_name": data["name"],
"bio": data.get("description"),
"follower_count": data.get("followers"),
"following_count": data.get("following"),
"verified": data.get("verified", False),
"verified_type": data.get("verifiedType"),
"profile_url": data.get("url"),
"profile_image_url": data.get("profilePicture"),
"created_at": data.get("createdAt"),
"unavailable_reason": data.get("unavailableReason"),
}
print(json.dumps(profile_row))
```
```go Go theme={null}
package main
import (
"encoding/json"
"io"
"log"
"net/http"
"os"
)
func main() {
username := "username"
req, err := http.NewRequest("GET", "https://xquik.com/api/v1/x/users/"+username, nil)
if err != nil {
log.Fatal(err)
}
req.Header.Set("x-api-key", "xq_your_api_key_here")
resp, err := http.DefaultClient.Do(req)
if err != nil {
log.Fatal(err)
}
defer resp.Body.Close()
body, err := io.ReadAll(resp.Body)
if err != nil {
log.Fatal(err)
}
var user map[string]any
if err := json.Unmarshal(body, &user); err != nil {
log.Fatal(err)
}
row := map[string]any{
"user_id": user["id"],
"username": user["username"],
"display_name": user["name"],
"bio": user["description"],
"follower_count": user["followers"],
"following_count": user["following"],
"verified": user["verified"],
"verified_type": user["verifiedType"],
"profile_url": user["url"],
"profile_image_url": user["profilePicture"],
"created_at": user["createdAt"],
"unavailable_reason": user["unavailableReason"],
}
if err := json.NewEncoder(os.Stdout).Encode(row); err != nil {
log.Fatal(err)
}
}
```
Use `GET /x/users/{id}` when a workflow needs one durable profile row 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` instead of logging
the full lookup response.
Store `id` as `user_id` plus `username`, `name`, `description`, `followers`,
`following`, `verified`, and `verifiedType`.
Use a numeric user ID for durable joins. Use username lookup when the
workflow starts from a handle.
Store `unavailable` and `unavailableReason` when returned, so retries,
support triage, and CRM syncs distinguish missing accounts from unavailable
profiles.
Use the returned `id` for followers, following, timelines, media, DMs,
follow checks, and monitor setup.
## Store a Twitter profile lookup
Keep the numeric X user ID as the stable key. Profile usernames, names, bios,
counts, verification, locations, links, and images can change between lookups.
| Profile column | Response field | CRM or warehouse rule |
| -------------------- | ------------------- | ---------------------------------------------------------------- |
| `x_user_id` | `id` | Use as the stable profile upsert and relationship key. |
| `x_username` | `username` | Store the current handle without using it as the durable key. |
| `display_name` | `name` | Preserve the public profile name observed during lookup. |
| `bio` | `description` | Store the profile bio when X returns it. |
| `follower_count` | `followers` | Preserve the observed follower count with the lookup time. |
| `following_count` | `following` | Preserve the observed following count with the lookup time. |
| `verified` | `verified` | Record the observed verification state. |
| `verified_type` | `verifiedType` | Distinguish returned business or government verification types. |
| `location` | `location` | Preserve the public profile location when supplied. |
| `profile_url` | `url` | Keep the public website link from the profile. |
| `profile_image_url` | `profilePicture` | Use the returned image in profile previews and review queues. |
| `account_created_at` | `createdAt` | Preserve the account creation timestamp when available. |
| `unavailable` | `unavailable` | Separate an unavailable profile from a successful active lookup. |
| `unavailable_reason` | `unavailableReason` | Route suspended, deactivated, or otherwise unavailable profiles. |
| Next workflow | Stable input | Route |
| ----------------------------- | --------------------------------------------- | ------------------------- |
| Follower export | `id` | `/x/users/{id}/followers` |
| Following export | `id` | `/x/users/{id}/following` |
| Profile timeline | `id` | `/x/users/{id}/tweets` |
| Profile replies | `id` | `/x/users/{id}/replies` |
| Profile media | `id` | `/x/users/{id}/media` |
| One follow relationship | Source and target profile IDs | `/x/followers/check` |
| Saved profile or audience job | Numeric profile ID in the selected tool input | `/extractions` |
## Path parameters
User ID or username (without `@`).
## Which user endpoint?
Use `GET /x/users/{id}` for one profile row by username or numeric user ID.
Use [`GET /x/users/search`](/api-reference/x/search-users) when the workflow
starts from a name, keyword, or partial handle.
Use [`GET /x/users/{id}/tweets`](/api-reference/x/user-tweets) for posts from
one profile.
Use [`GET /x/users/{id}/followers`](/api-reference/x/followers) when the next
step needs audience rows.
Use [`GET /x/followers/check`](/api-reference/x/check-follower) when the
workflow only needs one source-target relationship.
Use [`Create extraction`](/api-reference/extractions/create).
Create saved CSV/JSON/XLSX jobs. Export followers, following, timelines,
media, or search.
## Headers
Full account key. Sessions and OAuth also work.
`Bearer xq_your_guest_key_here` authenticates `paid_reads` guest keys. Direct MPP uses the `Payment ...` credential. Get it from the `WWW-Authenticate: Payment` challenge.
## Response
### 200 OK
User ID.
X username.
Display name.
Profile bio. Omitted if empty.
Follower count. Omitted if unavailable.
Following count. Omitted if unavailable.
Whether the user is verified. Omitted if unavailable.
Profile picture URL. Omitted if unavailable.
Profile location. Omitted if empty.
ISO 8601 account creation timestamp. Omitted if unavailable.
Total number of tweets posted. Omitted if unavailable.
Cover/banner image URL. Omitted if unavailable.
Total number of media tweets posted. Omitted if unavailable.
Website URL from profile. Omitted if empty.
Total number of tweets liked. Omitted if unavailable.
Whether the user has custom timelines (lists). Omitted if unavailable.
Whether the user is a Twitter 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 (suspended, deactivated). 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.
Whether the account has X Premium verification. Omitted if unavailable.
Normalized verification status. Omitted if unavailable.
Profile banner URL. Omitted if unavailable.
Whether the account protects its posts. Omitted if unavailable.
Role within a returned community context. Omitted outside community results.
```json theme={null}
{
"id": "987654321",
"username": "username",
"name": "Xquik",
"description": "X real-time data platform",
"followers": 10000,
"following": 500,
"verified": true,
"profilePicture": "https://pbs.twimg.com/profile_images/xquik/photo.jpg",
"coverPicture": "https://pbs.twimg.com/profile_banners/xquik/cover.jpg",
"location": "San Francisco",
"url": "https://xquik.com",
"createdAt": "2020-01-15T00:00:00.000Z",
"statusesCount": 5000,
"mediaCount": 120,
"favouritesCount": 430,
"isAutomated": false,
"possiblySensitive": false,
"hasCustomTimelines": false,
"pinnedTweetIds": ["1234567890"]
}
```
### 400 Invalid username
```json theme={null}
{ "error": "invalid_username" }
```
The provided username is empty or not a valid format.
### 401 Unauthenticated
```json theme={null}
{ "error": "unauthenticated" }
```
Missing or invalid API key. Check the `x-api-key` header value.
### 402 Payment required
Account keys get account options; guest keys get guest top-up only.
Anonymous calls receive a direct MPP `WWW-Authenticate: Payment` challenge plus a guest wallet creation action.
No checkout starts automatically. Confirm any payment action.
### 404 User not found
```json theme={null}
{ "error": "user_not_found" }
```
The X user does not exist. Check the username.
### 502 X API unavailable
```json theme={null}
{ "error": "x_api_unavailable" }
```
The read service returned an error. Retry after a short delay.
### 429 Rate Limit Exceeded
```json theme={null}
{ "error": "rate_limit_exceeded", "retryAfter": 60 }
```
Your tier rate limit was exceeded. Wait for the `Retry-After` header before retrying.
### 424 Dependency Failed
```json theme={null}
{ "error": "x_api_unavailable" }
```
The normalized v1 response contract can return 424 when the read service is unavailable.
**Next steps:** [Check Follower](/api-reference/x/check-follower) to verify follow relationships, or [Search Tweets](/api-reference/x/search-tweets) to find tweets from this user.