Skip to main content
GET
/
x
/
followers
/
check
Check follower
curl --request GET \
  --url https://xquik.com/api/v1/x/followers/check \
  --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.

5 credits per call · All plans from $0.00012/credit
Check follower verifies one known relationship without exporting a follower list. Pass the participant as source and the required brand, creator, or partner account as target. The response returns both directions: isFollowing for source-to-target proof and isFollowedBy for target-to-source context.
curl -G https://xquik.com/api/v1/x/followers/check \
  --data-urlencode "source=participant_handle" \
  --data-urlencode "target=brand_handle" \
  -H "x-api-key: xq_YOUR_KEY_HERE" | jq
The Node.js and Python snippets build a campaign audit event instead of printing the raw response page. Store the event with your campaign, entrant, or CRM row so reviewers can see the proof endpoint, the two handles checked, and the matched or not-matched state.

​
Campaign follow-check handoff

Use GET /api/v1/x/followers/check when a workflow already has both usernames and needs a single proof for a follow task. It is best for campaign entry validation, giveaway eligibility, creator partnerships, CRM qualification, and agent review queues where the participant handle is known before the check.

Single proof

Store one audit event per participant and required account pair.

Both directions

Store isFollowing as the required proof and isFollowedBy as reciprocal context.

Username inputs

Pass usernames without @. Use Get user first when you only have a display name, profile URL, or numeric ID.

Audit row

Persist the campaign ID, participant handle, required follow handle, endpoint, result booleans, and verification state.

Draw handoff

Use Create draw when winner selection also needs reply, repost, keyword, or unique-author filters.

Stopped audit

Treat 402 insufficient_credits as a stopped audit and resume after credits are available.

​
Query parameters

​
source
string
required
Source username without @. In campaign verification, this is usually the participant or entrant whose follow action is being checked.
​
target
string
required
Target username without @. In campaign verification, this is usually the brand, creator, partner, or required account that may be followed by the source.

​
Which verification endpoint?

Follow task

Use GET /x/followers/check for one participant-account follow proof.

Retweet task

Use GET /x/tweets/{id}/retweeters to page accounts that reposted one source tweet.

Reply task

Use GET /x/tweets/{id}/replies to check public replies under the source tweet.

Quote task

Use GET /x/tweets/{id}/quotes to inspect quote-tweet entries.

Follower export

Use GET /x/users/{id}/followers or a saved follower export when you need many followers for one profile.

Giveaway draw

Use POST /draws when Xquik should apply follow, repost, reply, keyword, and winner rules together.

​
Headers

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

​
Response

​
sourceUsername
string
The source username from the request.
​
targetUsername
string
The target username from the request.
​
isFollowing
boolean
true if the source user follows the target user.
​
isFollowedBy
boolean
true if the target user follows the source user.
{
  "sourceUsername": "participant_handle",
  "targetUsername": "brand_handle",
  "isFollowing": true,
  "isFollowedBy": false
}
Next steps: Campaign verification workflow for audit rows and draw handoffs, Get User to resolve profile details before checking, or Get Account to check remaining credits.
Last modified on May 25, 2026