Skip to main content
GET
/
x
/
users
/
{id}
/
followers-you-know
Get followers you know
curl --request GET \
  --url https://xquik.com/api/v1/x/users/{id}/followers-you-know \
  --header 'x-api-key: <api-key>'

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.

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 from $0.00012/credit · Accepts MPP
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.
curl https://xquik.com/api/v1/x/users/44196397/followers-you-know \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq
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.

Mutual rows

Store users[] as the mutual follower profile rows returned on this page.

Stable upserts

Store users[].id as x_user_id for CRM, warehouse, scoring, and agent dedupe.

Warm-intro labels

Store users[].username and users[].name for handles, owner review, routing, and handoff labels.

Profile context

Store users[].description, location, url, profilePicture, and coverPicture when returned.

Priority signals

Store users[].followers, users[].following, verified, and verifiedType for scoring and queue priority.

DM preflight

Store users[].canDm when returned, then use the DM endpoints only after a user-approved message flow.

Next page

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

​
id
string
required
Target X user ID as a numeric string. Use Get user first if you only have a username.

​
Query parameters

​
cursor
string
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?

Mutual followers

Use GET /x/users/{id}/followers-you-know for people who follow both the authenticated context and the target user.

All followers

Use GET /x/users/{id}/followers for all followers of one target profile.

Verified followers

Use GET /x/users/{id}/verified-followers when you only need verified followers of the target profile.

DM handoff

Use Send DM only after your workflow has a user-approved outreach step.

​
Headers

​
x-api-key
string
required
Your API key. Session cookie authentication is also supported.

​
Response

​
users
object[]
Array of mutual follower profiles.
​
has_next_page
boolean
Whether more results are available.
​
next_cursor
string
Opaque cursor for the next page. Empty string when no more results.
{
  "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..."
}
Related: Direct message workflow for user-approved outreach after users[].canDm, Send DM to send and store messageId, DM history to read participant-scoped context, Get followers, Get following, and Get verified followers.
Last modified on May 24, 2026