Skip to main content
GET https://xquik.com/api/v1/x/followers/check This route checks one follow relationship in both directions. Supply 2 accounts, each by user ID or username, and store both boolean results.
1 credit per call · All plans from $0.00012/creditDirect MPP at USD 0.00015 per call
Check follower verifies one known relationship without exporting a follower list. Pass the participant as source. Pass the required brand, creator, or partner account as target. Both accept a user ID, 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. Use isFollowing for source-to-target proof and isFollowedBy for target-to-source context.
The Node.js and Python snippets build a campaign audit event. They do not print the raw response page. Store the event with your campaign, entrant, or CRM row. Reviewers can then see the proof endpoint and the 2 handles checked. They can also see the matched or not-matched state.

Campaign follow-check handoff

Use GET /api/v1/x/followers/check when a workflow already has both usernames or @usernames. Use it when the workflow already has both user IDs or supported profile URLs. It returns one proof for a follow task. Use it for campaign entry validation, giveaway eligibility, and creator partnerships. Use it for 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 user ID, a username, @username, or supported X or Twitter profile URL. A number is a user ID. An x.com/i/user/<id> link names an account by ID too.

Audit row

Store 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

After 402 insufficient_credits, stop the audit. Resume after you add credits.

Query parameters

Choose fields

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 for many followers of one profile.

Giveaway draw

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

Headers

Response

200 OK

400 Invalid params

{ "error": "missing_params", "message": "Send both source and target, each a user ID or username.", "required": [ "source", "target" ] } One or both query parameters are missing. Provide both source and target. { "error": "invalid_username", "message": "Invalid source. Use a user ID, username, @username or X profile URL.", "parameter": "source" } The named parameter is invalid. Use a user ID, a username, @username, or supported X or Twitter profile URL. The API rejects foreign hosts, profile status URLs, credentials, and custom ports.

401 Unauthenticated

Missing or invalid API key. Check the 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 MPP WWW-Authenticate: Payment challenge plus a guest wallet creation action. No checkout starts automatically. Confirm any payment action.

502 X API unavailable

The read service returned an error. Retry after a short delay.

429 Rate limit exceeded

You exceeded your tier rate limit. Wait for the Retry-After header before retrying.

424 Dependency failed

The normalized v1 response contract can return 424 when the read service is unavailable.
Next steps. See Campaign verification workflow for audit rows and draw handoffs. Or use Get User to resolve profile details before checking. Or use Get Account to check remaining credits.

Response examples

  • 400 { "error": "missing_params" }
  • 401 { "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." }
  • 402 { "error": "insufficient_credits", "message": "Insufficient credits. Top up or subscribe to continue." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 424 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }
  • 502 { "error": "x_api_unavailable", "message": "X data source temporarily unavailable. Try again later." }
  • 503 { "error": "x_api_unavailable", "message": "Xquik is busy right now. Retry shortly." }