Skip to main content
DELETE https://xquik.com/api/v1/x/tweets/{id}/like
10 credits per call · All plans from $0.00012/creditA write that must sign in to your X account first adds 10 credits. Xquik refunds them if the sign-in fails. A sign-in that works keeps them, even if X then refuses the write. See the X sign-in fee.
Each request unlikes 1 tweet by ID. It changes 1 connected account’s like state. It never deletes the tweet, replies, reposts, or another account’s likes. Compare X’s separate Unlike Post endpoint.

Remove one Twitter like by ID

Put the exact Tweet ID in the path. Put its connected X account in the body. This endpoint accepts 1 Tweet ID per request. Store Tweet IDs as strings to preserve large identifiers.

Authenticate the Twitter account

Send an Xquik API key or OAuth 2.1 bearer token. The request never accepts an X password or session cookie. Keep credentials in server-side code. Reconnect the account after account_needs_reauth.

Approve the exact like removal

Show the tweet, author, Tweet ID, and acting account. Store the approver, approval time, and removal reason. Handle missing, private, or deleted tweets separately. Never replace an approved ID with another tweet.

Save an unlike receipt

Save the action before changing your local like record.

Confirm like removal

A 200 response is terminal. A 202 response still needs polling through statusUrl. Never resend an active action. After success, match the returned and requested Tweet IDs. If X (Twitter) reports no existing like, mark the account as unliked. Keep the prior state while terminal is false. Store the settled billing object after completion. Close already-unliked actions without another request.

Remove X (Twitter) likes in a controlled queue

This route has no mass-delete request. Process approved Tweet IDs separately. Give each account and Tweet ID a unique key. Use User Likes to collect candidate IDs. X shows likes only to their owner. That read can return 424 likes_unavailable. Follow every cursor before approving the list. After 429, wait for Retry-After. Never rotate accounts to bypass limits. Review X’s separate Unlike rate limits.

Prevent duplicate unlike requests

Create one idempotency key per account and Tweet ID. Reuse it only after an interrupted response. A 409 means that key already belongs to another payload. Create a new key only for a new removal intent.

Handle remove X (Twitter) likes errors

Never infer failure from a client timeout. Poll the returned action before another request.
  • On 400, correct the Tweet ID or account.
  • On 401, replace invalid Xquik authentication.
  • On 402, add credits before another unlike.
  • On 403, reconnect the selected X account.
  • On 409, keep the original action and payload.
  • On 422, review X’s rejection.
  • On 429, honor Retry-After before retrying.
  • On 500 or 503, follow safeToRetry and terminal.

Choose unlike, delete, or unretweet

Use this route only to remove one account’s like. Use Like Tweet to restore a like. Use Delete Tweet for an owned tweet. Use Unretweet for a repost. Unlike never removes replies, follows, bookmarks, or accounts.

Remove X (Twitter) likes questions

How to remove a like on Twitter with an API?

Send the Tweet ID and connected account. Poll the write action until it becomes terminal.

Can I remove all Twitter likes at once?

No. Process each approved Tweet ID separately. Store one key and action per removal.

Can I remove likes for multiple Twitter accounts?

Yes. Name one connected account per request. Keep its approval, key, and receipt together.

What are the risks of third-party like removal tools?

Never share your X password or session cookie. Review every account and Tweet ID.

Can I schedule X (Twitter) like removal?

Use your scheduler for approved Tweet IDs. This endpoint stores no future schedule.

Does unliking delete the original tweet?

No. It changes only the connected account’s like state.

Can I restore a removed like?

Yes. Call Like Tweet after new approval. Use a new key.

Does removing a like erase every historical record?

No. Earlier logs, exports, screenshots, or audits may remain. Do not treat a Twitter archive as proof of the current like state.

Headers

Path parameters

Body

Response

Durable write recovery

Send one unique Idempotency-Key per intended write. Replay the same account, target, payload, and media after a lost response. Keep the original key for that replay.
  1. Store id, the nested hash in request, billing, and statusUrl.
  2. Poll after Retry-After or pollAfterMs when terminal is false.
  3. Retry only when safeToRetry is true.
  4. Use a new key when nextAction.requiresNewIdempotencyKey is true.

200 terminal or 202 active

  • 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. Follow nextAction.
See Get Write Action Status for every lifecycle field and terminal state. That page also lists every billing field and retry rule.

Response examples

200 example

202 example

  • 400 { "error": "missing_idempotency_key", "message": "Idempotency-Key is required. Generate one unique key for this write.", "charged": false, "chargedCredits": "0", "retryable": false, "safeToRetry": true }
  • 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." }
  • 404 { "error": "account_not_found", "message": "X account not found. Connect it first at /dashboard/x-accounts." }
  • 409 { "error": "idempotency_conflict", "message": "Idempotency-Key was already used with a different request.", "charged": false, "chargedCredits": "0", "retryable": false, "safeToRetry": true }
  • 422 { "error": "x_rejected", "message": "X rejected this request. Check what you sent & the account on x.com before you try again." }
  • 429 { "error": "x_rate_limited", "message": "X rate limited this account. Try again in about 15 minutes. Send fewer requests from this account." }
  • 500 { "error": "x_write_failed", "message": "Write action failed unexpectedly. Contact support if this persists." }
  • 503 { "error": "write_tracking_unavailable", "message": "Write tracking unavailable. Try again.", "charged": false, "chargedCredits": "0", "retryable": true, "safeToRetry": true }