Skip to main content
GET https://xquik.com/api/v1/x/users/{id}/likes

When to read liked tweets

Use this route for the liked tweets of your connected X account. Pass that account’s user ID or username as id. Callers without a connected X account get 424 account_required. Use Connect X account to add one. Guest keys get 403 forbidden. X has shown likes only to their owner since 2024. When another profile reports likes and X hides them, the route returns 424 likes_unavailable. It does not return an empty 200. When your connected X accounts are busy, the route returns 503. Retry after the Retry-After delay. The output is tweet rows with engagement and pagination. Use media or timeline routes when you need posts the user wrote.
Requested result counts are upper bounds for paid authenticated calls. Remaining credits may not cover the full page or ID list. If so, Xquik returns fewer results. If zero paid results are affordable, it returns 402 insufficient_credits.
1 credit per result returned · All plans from $0.00012/credit

User likes handoff

GET /x/users/{id}/likes returns liked tweet rows from one account. Use it when a CRM, warehouse, recommendation job, or agent needs those rows. The examples above write JSON Lines rows with the liked-by user. Rows also hold the liked tweet ID, text, tweet URL, author ID, and username. They also hold the display name, follower count, verified state, and profile image URL. They also hold engagement counts, media URLs, and cursor fields. A worker can then resume from the last saved next_cursor.

Build a liked-tweet library

Use this route to collect tweets liked by one profile. Keep the source user ID with every tweet. A tweet can appear in several users’ liked feeds. Store fields that support review.
  • Tweet ID, text, author, and creation time.
  • Like, reply, repost, quote, and view counts.
  • Photo, video, or animated GIF URLs.
  • Source profile ID, cursor, and collection time.
A like does not prove agreement, ownership, or endorsement. Store the original author separately. For repeated collection, compare tweet IDs between snapshots. New IDs are newly observed likes. A missing ID proves little, because paging depth and like visibility can change. Use user media when the workflow needs tweets containing media from the profile itself. Use user tweets for the profile timeline. Each feed returns different tweets.

Compare liked-feed snapshots

Label every run as complete or partial. Compare only complete runs collected to the same paging depth. Keep first-seen and last-seen timestamps in your own store. The endpoint returns the current page, not a historical like event log. When a liked tweet disappears, record it as no longer observed. Do not claim the user removed the like unless another verified source confirms it. Tweet deletion or availability changes can produce the same observation. For review queues, link each row to the source tweet. Keep the liking profile separate from the tweet author. Store reviewer labels outside the tweet response. Use fixed values such as relevant, irrelevant, or needs review. Do not overwrite the original tweet text with notes. Keep both values in separate fields.

Path parameters

Query parameters

Tweet result filters

These optional filters apply to tweets[] returned by this route. They keep the same liked-tweets target. Xquik filters rows after it fetches each page. Selective filters can return fewer rows than an unfiltered page.See tweet filters for every filter. Common ones are fromUser, language, sinceDate, mediaType, minLikes, and hashtags.

Choose fields

Headers

Response

200 OK

400 Invalid user ID

{ "error": "invalid_user_id", "message": "Send a user ID, @username or profile URL, such as x.com/nasa." } The user ID is empty or invalid.

401 Unauthenticated

Missing or invalid API key.

402 Payment required

Account keys get account options. 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

When X hides a profile’s reported likes from other accounts, the route returns 424 likes_unavailable. Retrying does not help. It returns 424 x_api_unavailable when the read service is unavailable. Without a connected X account, the route returns 424 account_required. Connect one, then retry. { "error": "account_required", "message": "This read needs your own connected X account. Connect or restore it at dashboard.xquik.com/account, then retry." }

Response examples

  • 400 { "error": "invalid_input", "message": "Invalid input. Check the request body." }
  • 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": "user_not_found", "message": "X user not found. Check the username." }
  • 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." }