developers

The API your agents already speak.

One key drives REST calls, the MCP server, and the CLI. Posts your agents create go through the same queue and approval flow as the dashboard — nothing bypasses review.

REST

curl -X POST \
  https://alltwitter.example.com/api/v1/posts \
  -H "Authorization: Bearer at_…" \
  -d '{ "text": "…", "targets": [
    { "platform": "x" } ] }'

JSON in, JSON out. Bearer keys with scopes and per-plan rate limits.

MCP

{
  "mcpServers": {
    "alltwitter": {
      "url": "https://alltwitter.example.com/mcp",
      "headers": {
        "Authorization":
          "Bearer at_…"
      }
    }
  }
}

Claude, Cursor, and any MCP client get the same tools the REST API exposes.

CLI

atw login          # paste a key
atw post create \
  --text "Shipped it." \
  --target x \
  --schedule "tomorrow 9am"
atw queue list

The same surface, scriptable — cron jobs, CI steps, release notes to threads.

Scoped keys, minted in settings.

Keys are shown once at mint time — after that, only the prefix is listed. Scope each key to exactly what the agent calls.

posts:readposts:writeaccounts:readanalytics:readapprovals:manageadmin

Endpoint map

MethodPathWhat it does
GET/api/v1/accountsConnected publishing accounts
POST/api/v1/postsCreate a post — draft, scheduled, or queued
GET/api/v1/posts/queueThe publishing queue
GET/api/v1/posts/calendarScheduled + published history
GET/api/v1/approvalsDrafts awaiting review
POST/api/v1/approvals/:id/decideApprove or reject with a note
GET/api/v1/connectorsRSS/webhook connectors
GET/api/v1/evergreenEvergreen pool + rotation state
GET/api/v1/campaignsApproval-gated DM campaigns
GET/api/v1/analytics/overviewEngagement + usage summary

Approval decisions made through the API use the same statuses as the dashboard — programmatic replies and unapproved DM sends are blocked by design.

Mint a key, ship a post.

Sign in with X, open Settings → API keys, and your agents are publishing in minutes.