User Likes API

GET user/likes returns the tweets a target account has publicly liked, most recent first, in cursor-paginated pages of full Tweet objects. Requires the account's numeric user_id and a registered session. If the account hides its Likes tab, the endpoint returns an empty list rather than an error, at $0.0008 per call.

curl -X GET "https://example.com/user/likes?user_id=44196397"

{  "count": 1,  "next_cursor": "DAACCgAC...",  "tweets": [    {      "id": "1759123456789012345",      "text": "A tweet this account liked.",      "created_at": "Tue Feb 20 14:02:11 +0000 2026",      "author": {        "id": "745273",        "username": "naval",        "name": "Naval"      },      "favorite_count": 4821    }  ]}

{  "error": "bad_request",  "message": "Missing or malformed parameter. Fix the request before retrying."}

{  "error": "unauthorized",  "message": "The API key is missing, malformed, or revoked. Check the Authorization header."}

{  "error": "insufficient_credits",  "message": "Your balance is exhausted. Top up your credits to continue."}

{  "error": "not_found",  "message": "The resource does not exist, for example a deleted tweet or a private account."}

{  "error": "rate_limited",  "message": "Too many requests. Back off and retry with exponential backoff."}

{  "error": "server_error",  "message": "Something failed on our side. Retry with backoff; if it persists, contact support."}

Pricing

When to use

Use this when you need the tweets a specific account has liked, not posted, for example building a like-based interest graph or surfacing what content a user engages with. Reach for a different User Reads endpoint (like user tweets) when you need what the account posted rather than what it liked.

Notes

• Needs a session for the account you are reading: either register one once (POST /customer/session), or pass per-call inline credentials as x-auth-token and x-ct0 request headers, which let a single API key act as many accounts. Returns 409 session_required if neither is supplied, 401 session_dead when the session has expired.
• Most accounts hide their likes; expect an empty tweets array unless the target made its Likes tab public (or it is your own account).

Pagination

This endpoint is cursor-paginated and returns roughly 20 records per call. Pass the next_cursor from each response back as the cursor parameter to read the next page. Stop when the records array comes back empty: follower-graph endpoints return a non-null cursor even on the final page, so the empty array is the only reliable stop signal. See Pagination for the full loop.

Related endpoints

• User Info by Username: Fetch a full profile by @handle.
• User Info by ID: Fetch a full profile by numeric user ID.

FAQ

Why did I get an empty tweets array with has_more false for a valid user_id?

The account has hidden its Likes tab. Twitter/X lets users disable public visibility of likes, and when that happens the endpoint returns an empty tweets array rather than an error, since there is no way to distinguish 'no likes' from 'likes hidden' at the API level. Check the account's is_liked_tweets_public status via a user info endpoint if you need to tell these cases apart.

How do I page through more than 100 liked tweets?

Set count up to its cap of 100 per request (default is 20), then pass the next_cursor value from the response into the cursor param on your next call. Keep paging while has_more is true; next_cursor is opaque and should not be parsed or constructed manually.