> ## 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 followers you know
> Retrieve mutual X followers between the authenticated context and one target user for warm-intro, CRM, scoring, and agent workflows
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 result returned** · [All plans](https://xquik.com/#pricing) from \$0.00012/credit · Accepts [MPP](/mpp/overview)
Get followers you know returns mutual followers between the authenticated
context and one target X user. It is also useful as a mutual followers API,
followers you know API, X mutual followers API, or Twitter mutual followers
API. The canonical endpoint remains
`GET /api/v1/x/users/{id}/followers-you-know`.
```bash First page theme={null}
curl https://xquik.com/api/v1/x/users/44196397/followers-you-know \
-H "x-api-key: xq_YOUR_KEY_HERE" | jq
```
```bash Next page theme={null}
curl -G https://xquik.com/api/v1/x/users/44196397/followers-you-know \
--data-urlencode "cursor=abc123" \
-H "x-api-key: xq_YOUR_KEY_HERE" | jq
```
```javascript Node.js theme={null}
const userId = "44196397";
const response = await fetch(`https://xquik.com/api/v1/x/users/${userId}/followers-you-know`, {
headers: { "x-api-key": "xq_YOUR_KEY_HERE" },
});
const data = await response.json();
const mutualRows = data.users.map((user) => ({
target_user_id: userId,
x_user_id: user.id,
username: user.username,
display_name: user.name,
can_dm: user.canDm ?? null,
follower_count: user.followers ?? null,
verified: user.verified ?? false,
verified_type: user.verifiedType ?? null,
profile_image_url: user.profilePicture ?? null,
}));
const nextCursor = data.has_next_page ? data.next_cursor : null;
const checkpoint = { target_user_id: userId, next_cursor: nextCursor };
for (const row of mutualRows) {
process.stdout.write(`${JSON.stringify(row)}\n`);
}
process.stdout.write(`${JSON.stringify(checkpoint)}\n`);
```
```python Python theme={null}
import json
import requests
user_id = "44196397"
response = requests.get(
f"https://xquik.com/api/v1/x/users/{user_id}/followers-you-know",
headers={"x-api-key": "xq_YOUR_KEY_HERE"},
)
data = response.json()
mutual_rows = [
{
"target_user_id": user_id,
"x_user_id": user["id"],
"username": user["username"],
"display_name": user["name"],
"can_dm": user.get("canDm"),
"follower_count": user.get("followers"),
"verified": user.get("verified", False),
"verified_type": user.get("verifiedType"),
"profile_image_url": user.get("profilePicture"),
}
for user in data["users"]
]
next_cursor = data["next_cursor"] if data["has_next_page"] else None
checkpoint = {"target_user_id": user_id, "next_cursor": next_cursor}
for row in mutual_rows:
print(json.dumps(row))
print(json.dumps(checkpoint))
```
The Node.js and Python snippets shape durable mutual follower rows instead of
printing the full response page. Persist the rows with the checkpoint so a
worker can resume pagination with `next_cursor` without duplicating already
imported profiles.
## Direct mutual followers handoff
Use `GET /x/users/{id}/followers-you-know` when a sales, community, recruiting, support, CRM, or agent workflow needs one JSON page of mutual followers for a target user. The path `id` is the target numeric X user ID. The endpoint returns people who follow both the authenticated context and the target user.
Store `users[]` as the mutual follower profile rows returned on this page.
Store `users[].id` as `x_user_id` for CRM, warehouse, scoring, and agent dedupe.
Store `users[].username` and `users[].name` for handles, owner review, routing, and handoff labels.
Store `users[].description`, `location`, `url`, `profilePicture`, and `coverPicture` when returned.
Store `users[].followers`, `users[].following`, `verified`, and `verifiedType` for scoring and queue priority.
Store `users[].canDm` when returned, then use the DM endpoints only after a user-approved message flow.
Store `has_next_page` and `next_cursor`; pass `next_cursor` back as `cursor` only when `has_next_page` is true.
Direct mutual followers cost 1 credit per user returned. Low credit balances can return fewer users than a full page; zero affordable results return `402 insufficient_credits`. For MPP callers, this endpoint is billed as a session at USD 0.00015 per user returned.
## Path parameters
Target X user ID as a numeric string. Use [Get user](/api-reference/x/get-user)
first if you only have a username.
## Query parameters
Pagination cursor from `next_cursor` in a previous response. Omit for the
first page. Pass a cursor only when `has_next_page` is true.
## Which follower graph endpoint?
Use `GET /x/users/{id}/followers-you-know` for people who follow both the
authenticated context and the target user.
Use [`GET /x/users/{id}/followers`](/api-reference/x/followers) for all
followers of one target profile.
Use [`GET /x/users/{id}/verified-followers`](/api-reference/x/verified-followers)
when you only need verified followers of the target profile.
Use [`Send DM`](/api-reference/x-write/send-dm) only after your workflow has
a user-approved outreach step.
## Headers
Your API key. Session cookie authentication is also supported.
## Response
Array of mutual follower profiles.
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.
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.
Whether more results are available.
Opaque cursor for the next page. Empty string when no more results.
```json theme={null}
{
"users": [
{
"id": "987654321",
"username": "xquikcom",
"name": "Xquik",
"followers": 10000,
"verified": true,
"profilePicture": "https://pbs.twimg.com/profile_images/xquik/photo.jpg"
}
],
"has_next_page": true,
"next_cursor": "DAADDAABCgABF..."
}
```
```json theme={null}
{ "error": "invalid_user_id" }
```
The user ID is empty or invalid.
```json theme={null}
{ "error": "unauthenticated" }
```
Missing or invalid API key.
```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:** [Direct message workflow](/guides/direct-message-workflow) for user-approved outreach after `users[].canDm`, [Send DM](/api-reference/x-write/send-dm) to send and store `messageId`, [DM history](/api-reference/x/dm-history) to read participant-scoped context, [Get followers](/api-reference/x/followers), [Get following](/api-reference/x/following), and [Get verified followers](/api-reference/x/verified-followers).