Skip to main content
POST
Reference example
Like a tweet on behalf of the authenticated source user. Proxies the official X v2 POST /2/users/{id}/likes endpoint, routed through the AIsa gateway at https://api.aisa.one/apis/v1/twitter/like_twitter.

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

Idempotency

Liking a tweet the source user has already liked is a no-op. The endpoint still returns 200 with { "data": { "liked": true } }. Safe to retry.

Common 4xx causes

  • 400 invalid-request — missing or non-numeric tweet_id
  • 403 client-forbidden — OAuth session missing the like.write scope. Re-link via auth_twitter.
  • 404 resource-not-found — tweet doesn’t exist or isn’t visible to the source user (e.g., a protected account the source user doesn’t follow).
See Error Codes and Rate Limits for more.

Link an X Account

Start the OAuth flow this endpoint requires.

Post a Tweet

Create tweets you (or your agents) can like.

Follow a User

Another write endpoint using the same OAuth session.

Request contract

Complete OpenAPI definition Effective request and pricing declaration (including authentication and referenced schemas):

Cost and request rules

Published reference price: $0.015 USD per successful request. Account-specific pricing and final settlement may differ. Published reference values are not an account-specific quote or a settled charge. For endpoints supporting X-AISA-Cost-Mode: quote, obtain a free quote for your exact request before execution; reconcile the settled cost with response metadata and Usage Logs. USD amounts use 1,000,000 integer micro-USD per dollar.
  • Default request reference estimate (USD): 0.015
  • Cost contract: fixed_success
  • Published reference multiplier: 1.0
  • Settlement evidence source: request_snapshot

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
tweet_id
string
required

Numeric ID of the tweet to like. Must match X's regex ^[0-9]{1,19}$.

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

"1346889436626259968"

Response

Like succeeded (or was already in place).

data
object