Skip to main content
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

​
Authentication

Send your API key on every request:
Write actions (post, like, follow, DM send) also require a saved Twitter cookie or auth_token on the request. See Authentication for examples across cURL, Python, JavaScript, and Java.

​
Response format

Successful responses use a consistent envelope:
Errors return non-2xx HTTP status codes with a JSON body. See Error Handling for status-by-status recovery guidance.

​
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:
Open Get Balance for the full schema.

​
Endpoint groups

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

​
Agent and SDK paths

​
Operational guides

  • Error Handling — HTTP status recovery, MCP errors, and write retries
  • Rate Limits — throughput guidance and 429 backoff
  • Write Actions — cookie / auth_token, duplicate checks, and 403 credits
  • 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.