Relationships
Twitter follower checker API for X accounts
Check whether one X user follows another in either direction for giveaway eligibility, campaign proof, CRM flags, and relationship audits. See fields.
- 200
- 400
- 401
- 402
- 424
- 429
- 502
GET
Twitter follower checker API for X accounts
Use this Twitter follower checker API to verify one relationship in either direction. Supply 2 usernames and store both boolean results.
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.
One or both query parameters are missing. Provide both
The named parameter is invalid. Use a username,
Missing or invalid API key. Check the
The read service returned an error. Retry after a short delay.
Your tier rate limit was exceeded. Wait for the
The normalized v1 response contract can return 424 when the read service is unavailable.
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. Each input accepts a username, @username, or
supported X or Twitter profile URL. Xquik resolves profile URLs and converts
both usernames to lowercase before lookup. The response returns both directions:
isFollowing for source-to-target proof and isFollowedBy for
target-to-source context.Campaign follow-check handoff
UseGET /api/v1/x/followers/check when a workflow already has both usernames,
@usernames, or supported profile URLs and needs one proof for a follow task.
Use it for campaign entry validation, giveaway eligibility, creator
partnerships, CRM qualification, and agent review queues.
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.Accepted inputs
Pass a username,
@username, or supported X or Twitter profile URL.
Numeric user IDs are not accepted. Use Get user
first when you only have a 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
string
required
Source username,
@username, or supported X or Twitter profile URL. Xquik
resolves profile URLs and converts the username to lowercase. In campaign
verification, this is usually the participant or entrant.string
required
Target username,
@username, or supported X or Twitter profile URL. Xquik
resolves profile URLs and converts the username to lowercase. In campaign
verification, this is usually the required brand, creator, or partner account.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
string
Full account key. Sessions and OAuth also work.
string
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
string
Canonical lowercase username resolved from
source.string
Canonical lowercase username resolved from
target.boolean
true if the source user follows the target user.boolean
true if the target user follows the source user.400 Invalid params
source and target.
@username, or supported X or Twitter profile URL. Numeric IDs, foreign hosts, profile status URLs, credentials, and custom ports are rejected.
401 Unauthenticated
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 MPPWWW-Authenticate: Payment challenge plus a guest wallet creation action.
No checkout starts automatically. Confirm any payment action.
502 X API unavailable
429 Rate limit exceeded
Retry-After header before retrying.
424 Dependency failed
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.
- 200
- 400
- 401
- 402
- 424
- 429
- 502
Twitter follower checker API for X accounts