Export mutual X followers as paginated JSON for warm-intro, CRM, scoring, and agent workflows
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.
402 insufficient_credits.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 endpoint returns people who follow both the authenticated context and the target user.
users[] as the mutual follower profile rows returned on this page.users[].id as x_user_id for CRM, warehouse, scoring, and agent dedupe.users[].username and users[].name for handles, owner review, routing, and handoff labels.users[].description, location, url, profilePicture, and coverPicture when returned.users[].followers, users[].following, verified, and verifiedType for scoring and queue priority.users[].canDm when returned, then use the DM endpoints only after a user-approved message flow.has_next_page and next_cursor; pass next_cursor back as cursor only when has_next_page is true.402 insufficient_credits. For MPP callers, this endpoint is billed as a session at USD 0.00015 per user returned.
next_cursor value from the previous response to fetch the next page.users[].canDm, Send DM to send and store messageId, DM History to read participant-scoped context, Followers, Following, and Verified Followers.