Skip to main content
POST
https://api.aisa.one/apis/v1
/
twitter
/
unfollow_twitter
Unfollow a user on X/Twitter
curl --request POST \
  --url https://api.aisa.one/apis/v1/twitter/unfollow_twitter \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "target_user_id": "2244994945"
}
'
{
  "data": {
    "following": false
  }
}
Unfollow a user on X/Twitter on behalf of the authenticated source user. This is a proxy for the official X v2 DELETE /2/users/{source_user_id}/following/{target_user_id} endpoint, exposed through the AIsa gateway at https://api.aisa.one/apis/v1/twitter/unfollow_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 — that endpoint kicks off the OAuth flow and stores the resulting session against your AIsa key, so you do not pass OAuth tokens in the request body here.
  • The X session must hold the following scopes: follows.write, tweet.read, users.read.
Looking to unfollow by @username instead of numeric ID? Resolve the user first with GET /twitter/user/info, then pass the returned id as target_user_id.

​
Response fields

FieldTypeMeaning
data.followingbooleanfalse once the source user no longer follows the target. Returned as false even if the source user wasn’t following the target to begin with — unfollow is idempotent.

​
Idempotency

Calling unfollow_twitter against a user you’re not following is a no-op. The endpoint still returns 200 with { "data": { "following": false } }. This matches X’s own behavior and means you can safely retry. For the full set of error responses and retry guidance, see Error Codes. Write endpoints count toward your standard key RPM/TPM — see Rate Limits.

Link an X Account

Start the OAuth flow that enables this endpoint.

Follow a User

The inverse operation.

Check Follow Relationship

Verify the relationship before calling.

Authorizations

​
Authorization
string
header
required

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
​
target_user_id
string
required

Numeric ID of the X/Twitter user to unfollow. Must match the X regex ^[0-9]{1,19}$.

Pattern: ^[0-9]{1,19}$
Example:

"2244994945"

Response

Unfollow succeeded (or the source user wasn't following the target to begin with).

​
data
object