API Overview

TwexAPI REST reference — authentication, response format, pagination, errors, rate limits, and endpoint groups.

TwexAPI exposes a REST API at https://api.twexapi.io for X/Twitter reads, writes, search, followers, DMs, lists, communities, articles, and account utilities.

Use this page as the entry point before opening individual endpoint pages in the sidebar.

Base URL

https://api.twexapi.io

Authentication

Send your API key on every request:

Authorization: Bearer YOUR_API_KEY

Public-data reads require an API key. Account-private operations such as delegate invitation lookup also require the authorized account’s X cookie or auth_token.

Response format

Successful responses use a consistent envelope:

{
  "code": 200,
  "msg": "success",
  "data": {}
}

Errors return non-2xx HTTP status codes with a JSON body. See Error Handling for recovery patterns and Error Reference for endpoint-specific messages and X error codes.

Pagination

Many list and search endpoints return cursor fields such as has_next_page, next_cursor, or page tokens inside data. Pass the cursor from the previous response unchanged on the next request. Preserve cursors outside chat or workflow memory when jobs must resume after failures.

Check balance

Inspect remaining credits before large exports:

curl --request GET \
  --url 'https://api.twexapi.io/balance' \
  --header 'Authorization: Bearer YOUR_API_KEY'

Open Get Balance for the full schema.

High-Intent Use Cases & Solutions

Find the exact endpoint for your Twitter data scraping, monitoring, and automation needs:

Endpoint groups

Browse generated pages under Endpoints in the sidebar, or jump to common groups:

Agent and SDK paths

Operational guides

• Error Reference — endpoint-specific messages, X codes, and retry decisions
• Error Handling — HTTP status recovery, MCP errors, and write retries
• Rate Limits — throughput guidance and 429 backoff
• Authentication — API keys, Bearer headers, and write credentials

What TwexAPI does not expose today

TwexAPI does not ship native account monitors, event webhooks, or async extraction jobs as first-class API products. Use scheduled REST calls (Prefect, n8n, cron) or no-code platform webhooks to receive agent handoffs, then continue with direct API requests.

Data handling

TwexAPI does not maintain an archive or database of X content. We do not persist copies of public posts, X Articles, direct-message content, or AI chat content obtained through customer requests.

Requests are processed in transit. We retain only limited operational information necessary for security, abuse prevention, billing, and service reliability, such as request timestamps, endpoint usage, status codes, and credit consumption. We do not sell or provide archived X-content datasets.