Post from your own code

A small REST API over the same pipeline the app uses — including the pre-flight checks and the per-network delivery isolation. JSON in, JSON out, bearer auth.

Authentication

Create a key in the app under API keys. It is shown once — we store only a hash, so it cannot be recovered afterwards. Send it as a bearer token.

Authorization: Bearer pilot_your_key_here

Endpoints

Post to every network

Omit schedule and it drops into your next free queue slot. Pass "now" to publish immediately, or an ISO timestamp for a specific time.

curl -X POST https://attentionpilot.com/api/v1/posts \
  -H "Authorization: Bearer $PILOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "caption": "We shipped per-network retries today.",
    "accounts": "all"
  }'

Pick networks by name

accounts takes account ids, platform names, or handles — whichever you have to hand.

{
  "caption": "Short version for the fast networks.",
  "accounts": ["x", "bluesky", "threads"],
  "schedule": "2026-08-01T09:00:00Z"
}

What comes back

Publishing immediately returns the per-network outcome, because each network succeeds or fails on its own. A partly-published post is a normal result, not an error.

{
  "id": "0f3c…",
  "status": "partial",
  "targets": [
    { "platform": "bluesky", "status": "posted",
      "url": "https://bsky.app/profile/you/post/3k…" },
    { "platform": "x", "status": "failed",
      "error": "312 chars — X allows 280." }
  ]
}

Errors worth handling