Skip to main content
POST
How Do You Remove a Twitter Follower? Xquik API

How Do You Remove a Twitter Follower?

Use this endpoint to remove 1 follower from a connected X account. Put the follower’s numeric X user ID in the path. Name the connected account in the JSON body. Then approve, poll, and verify the inbound relationship change. X also documents manual follower removal. Its help page explains that a removed account may follow again.
10 credits per call · All plans from $0.00012/credit
Action-specific rate limit: Remove Follower shares 20 requests per minute and 400 per day with follow actions. The POST tier also allows 120 requests per minute. A breached limit returns 429 Too Many Requests.

Resolve the Follower and Connected Account

Read Followers before choosing a target. Resolve the current username to a stable numeric X user ID. Usernames and profile names can change. The numeric ID keeps the moderation record tied to one account. Show the follower ID, username, profile name, and acting account. Also show the moderation reason before approval. The path {id} identifies the follower you will remove. The body field account identifies whose follower list will change. Never infer spam from a username, avatar, or missing profile field. Choose the unwanted follower with your approved moderation rule. This helps you identify and remove the right account. Store the reviewer, reason, and evidence outside this public request.

Remove Followers on Twitter Safely

Create 1 idempotency key for each intended removal. Reuse that key only after an interrupted network request. Never reuse it for another follower or connected account. This route accepts 1 follower ID per request. It provides no bulk body for mass follower removal. Queue approved follower IDs as separate write actions instead. Each row needs its own reason, approval, and idempotency key. A social media team can review the queue before dispatch. Use the queue to manage your Twitter account safely. Do not let a temporary failure erase successful removals. Store each returned action ID beside its target follower ID.

Poll and Verify the Removal

Store id, request.hash, billing, and statusUrl immediately. An HTTP 200 response represents a terminal write action. An HTTP 202 response represents an active write action. Poll the same statusUrl while terminal remains false. Never submit another removal just because the first action is active. A second request could add a duplicate job. Keep the original idempotency key for an exact network replay. Read Followers after the action becomes terminal. You can also call Check Follower. Set the removed account as the source relationship participant. Set the connected account as the target participant. Confirm the inbound follower relationship is absent.

Choose Remove Follower, Unfollow, or Block

Remove Follower ends one inbound relationship. The selected account stops following your connected X account. It does not make your connected account unfollow the selected account. Use Unfollow for that outbound relationship. Keep both actions separate in every moderation workflow. The accounts do not need a mutual follow relationship. Follower removal is also different from blocking. A removed follower can follow your public account again. They can ask to follow your protected account again. Block the account through X when it must not follow again. This endpoint lets you remove a follower without blocking them.

Review Bots, Private Accounts, and Bulk Queues

This endpoint does not detect bots, spam, or inactive accounts. Check profiles and follower relationships before you approve a removal. Never treat a protected profile as proof of abusive behavior. Private and public accounts use the same Xquik request shape. However, X controls whether the removed account can follow again. Do not promise a permanent audience restriction from this write. Store the terminal result, then verify the live follower relationship. For multiple targets, process one approved queue row at a time. Throttle the queue to every documented rate limit.

Handle Remove Follower API Errors

Fix the follower ID or connected account after 400. Replace Xquik authentication after 401. Add credits after 402; reconnect the account after 403. Keep the original action after an idempotency conflict at 409. Fix rejected input after 422. Honor Retry-After after 429. After 500 or 503, inspect safeToRetry before retrying.

Twitter Follower Removal Questions

How to Remove Followers on Twitter with an API?

Resolve each follower to a numeric ID. Send one approved request per follower, then poll every action.

How Do You Remove a Follower from Twitter Without Blocking?

Call this endpoint for the inbound relationship. The removed account may still follow the connected account again.

Can I Remove All Followers or Bot Followers at Once?

No batch body is available. Review suspected bots first, then queue one approved target per request.

Does X Notify a Removed Follower?

No response field tells you whether X sent a notification. Your final check should cover only the follower relationship.

Can I Unfollow Accounts with This Endpoint?

No. Use Unfollow when the connected account follows another account. Use Remove Follower when someone follows you.

Does This Work for Mobile, Desktop, or Private Accounts?

The REST request works from any HTTP client. It does not depend on X’s mobile or desktop interface.

How Do I Get an API Key?

Create an Xquik API key in the dashboard. You can also send an OAuth 2.1 bearer token.

Headers

string
Send your Xquik API key. Generate one from the dashboard.
string
Send Bearer <token> instead of x-api-key when using OAuth 2.1.
string
required
Unique key for this intended write. Reuse it only for an exact network replay.
string
required
Must be application/json.

Path parameters

string
required
The X user ID of the follower to remove.

Body

string
required
X username or account ID of your connected account whose follower list should be updated.

Response

Durable Write Recovery

Send one unique Idempotency-Key per intended write. Reuse it only for the same account, target, payload, and media.
  1. Store id, the nested hash in request, billing, and statusUrl.
  2. Poll after Retry-After or pollAfterMs when terminal is false.
  3. Trust safeToRetry and nextAction before any new write.

200 Terminal or 202 Active

Store terminal results. Poll active actions without creating another write.
  • After HTTP 200, store the result and settled billing.
  • After HTTP 202, poll the same action. Never submit another write.
  • After HTTP 400, fix the named field. Use a new idempotency key.
  • After HTTP 401, fix authentication. Do not retry unchanged.
  • After HTTP 402, fund the account before another write.
  • After HTTP 403, reconnect the account.
  • After HTTP 409, keep the original action. Use a new key for new input.
  • After HTTP 422, fix the rejected request before retrying.
  • After HTTP 429, wait for Retry-After. Preserve the same key.
  • After HTTP 500, retry only when safeToRetry is true.
  • After HTTP 503, poll while terminal is false.
See Get Write Action Status for every lifecycle field, terminal state, billing field, and retry rule.