Unlike a tweet
Post & Actions
Unlike a Tweet
Remove the source user’s like from a tweet. Proxies the official X v2 unlike-post endpoint through the AIsa gateway.
POST
Unlike a tweet
Remove the source user’s like from a tweet. Proxies the official X v2
DELETE /2/users/{id}/likes/{tweet_id} endpoint, exposed through the AIsa gateway at https://api.aisa.one/apis/v1/twitter/unlike_twitter. AIsa uses POST for consistency with the other Twitter write endpoints.
Prerequisites
- An AIsa API key (Bearer token for every request).
- A one-time OAuth authorization for the source user account. Link your X account by calling
POST /apis/v1/twitter/auth_twitter— AIsa stores the session against your API key and uses it automatically on every write call. - The X session must hold
like.write,tweet.read,users.read.
Response fields
| Field | Type | Meaning |
|---|---|---|
data.liked | boolean | false once the like has been removed. Returned as false even if the source user hadn’t liked the tweet to begin with — unlike is idempotent. |
Idempotency
Unliking a tweet the source user has not liked is a no-op. The endpoint still returns200 with { "data": { "liked": false } }. Safe to retry.
Common 4xx causes
400 invalid-request— missing or non-numerictweet_id403 client-forbidden— OAuth session missing thelike.writescope. Re-link viaauth_twitter.404 resource-not-found— tweet doesn’t exist or isn’t visible to the source user.
Related
Link an X Account
Start the OAuth flow this endpoint requires.
Like a Tweet
The inverse operation.
Post a Tweet
Another write endpoint using the same OAuth session.
Authorizations
Your AIsa API key. The authenticated source user (the account doing the follow) is determined by the OAuth session attached to your key.
Body
application/json
Numeric ID of the tweet to unlike. Must match X's regex ^[0-9]{1,19}$.
Pattern:
^[0-9]{1,19}$Example:
"1346889436626259968"
Response
Unlike succeeded (or the source user hadn't liked the tweet to begin with).