Back to Directory
T

Twitter actions via AIsa

Other
Write actions against X/Twitter, routed through the AIsa gateway. Modeled after the official X v2 API endpoints (e.g., POST /2/users/{id}/following).

About Twitter actions via AIsa

Review the Service identity, supported languages, protocol versions, and source metadata discovered by the directory.

Service details

Service Id
0ead6386-9c0b-4090-a3c9-e88f3fa118fe
Service origin
https://api.aisa.one
ListedSeptember 24, 2026, 6:42 PM
Last checkedSeptember 24, 2026, 8:02 PM

Protocol details

SourceOpenAPI

Endpoints

Endpoint details are saved from the OpenAPI document. Authentication requirements and prices are advertised information, not a verified payment or access guarantee. The document may contain additional endpoints.Open OpenAPI document
POST/twitter/auth_twitter

Link an X/Twitter account (start OAuth)

Start the OAuth flow that links a user's X/Twitter account to the AIsa API key on the request. Call this once per source user. AIsa returns an authorization URL — the user opens it in a browser, approves the requested scopes, and X redirects back to AIsa's fixed callback. AIsa stores the resulting session against your API key, and every subsequent Twitter write call (e.g., `POST /twitter/follow_twitter`) uses that session automatically. The returned `auth_url` is short-lived; generate a fresh one every time the user needs to (re-)link.Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.
POST/twitter/follow_twitter

Follow a user on X/Twitter

Make the authenticated source user follow the given target user on X/Twitter. Mirrors the [official X v2 `POST /2/users/{id}/following` endpoint](https://docs.x.com/x-api/users/follow-user), routed through the AIsa gateway. **Authentication.** This is a write action that requires an OAuth session for the source user, attached to your AIsa API key. Link your X account once by calling `POST /apis/v1/twitter/auth_twitter` — AIsa then uses that session automatically for every write request sent with your key. **Scopes.** The underlying X session must hold `follows.write`, `tweet.read`, and `users.read`.Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.
POST/twitter/like_twitter

Like a tweet

Like a tweet on behalf of the authenticated source user. Mirrors the [official X v2 `POST /2/users/{id}/likes` endpoint](https://docs.x.com/x-api/users/like-post), routed through the AIsa gateway. **Authentication.** Requires an OAuth session for the source user, attached to your AIsa API key. Link the account once via `POST /apis/v1/twitter/auth_twitter`. **Scopes.** The underlying X session must hold `like.write`, `tweet.read`, and `users.read`. Liking a tweet already liked is a no-op and still returns `200` with `liked: true`.Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.
POST/twitter/post_twitter

Post or edit a tweet

Publish a new tweet on behalf of the authenticated source user, or edit an existing tweet. Mirrors the [official X v2 `POST /2/tweets` endpoint](https://docs.x.com/x-api/posts/create-post), routed through the AIsa gateway. **Authentication.** Requires an OAuth session for the source user, attached to your AIsa API key. Link the account once via `POST /apis/v1/twitter/auth_twitter`. **Scopes.** The underlying X session must hold `tweet.read`, `tweet.write`, and `users.read`. **Mutually exclusive fields.** `media`, `poll`, `quote_tweet_id`, and `card_uri` cannot be combined in the same request. At most one of them may be set.Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.
POST/twitter/unfollow_twitter

Unfollow a user on X/Twitter

Make the authenticated source user unfollow the given target user on X/Twitter. Mirrors the [official X v2 `DELETE /2/users/{source_user_id}/following/{target_user_id}` endpoint](https://docs.x.com/x-api/users/unfollow-user), routed through the AIsa gateway. Uses POST (not DELETE) for consistency with the other AIsa Twitter write actions. **Authentication.** Requires an OAuth session for the source user, attached to your AIsa API key. Link the account once via `POST /apis/v1/twitter/auth_twitter`. **Scopes.** The underlying X session must hold `follows.write`, `tweet.read`, and `users.read`. Unfollowing a user you don't currently follow is a no-op and still returns `200` with `following: false`.Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.
POST/twitter/unlike_twitter

Unlike a tweet

Remove the source user's like from a tweet. Mirrors the [official X v2 `DELETE /2/users/{id}/likes/{tweet_id}` endpoint](https://docs.x.com/x-api/users/unlike-post), routed through the AIsa gateway. Uses POST (not DELETE) for consistency with the other AIsa Twitter write actions. **Authentication.** Requires an OAuth session for the source user, attached to your AIsa API key. Link the account once via `POST /apis/v1/twitter/auth_twitter`. **Scopes.** The underlying X session must hold `like.write`, `tweet.read`, and `users.read`. Unliking a tweet the source user has not liked is a no-op and still returns `200` with `liked: false`.Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.
POST/twitter/upload_media

Upload media (pre-upload for tweets)

Upload a single image, GIF, or video and receive a `media_id` you can attach to a tweet via [`post_twitter`](/api-reference/twitter/post_twitter-post-twitter) (`media.media_ids`). Routed through the AIsa gateway at `https://api.aisa.one/apis/v1/twitter/upload_media`. **Content type — `multipart/form-data` only.** Send the file as a multipart form part. **Do not send a JSON body** — a JSON request is rejected with `400 "upload_media requires multipart/form-data with a single media file field"`. **Two-step media flow.** 1. `POST /apis/v1/twitter/upload_media` with the file → returns `media_id`. 2. `POST /apis/v1/twitter/post_twitter` with `{ "media": { "media_ids": ["<media_id>"] } }`. Alternatively, `post_twitter` accepts inline file parts via `media_files` in a single multipart request, skipping this pre-upload step. **Authentication.** Requires an OAuth session for the source user, attached to your AIsa API key. Link the account once via [`POST /apis/v1/twitter/auth_twitter`](/api-reference/twitter/post…Price unavailableThe operation requires declared authentication; API keys, bearer tokens and other schemes are not evidence of AEP support.