Post from your own code

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

Upload media, get an id back

For videos use presign, PUT the bytes to storage, then complete. The agent guide has the full flow. For images up to 4 MiB, upload once to /api/v1/media and attach the returned id to any post. When the bytes are on your machine, send multipart form-data:

curl -X POST https://attentionpilot.com/api/v1/media \
  -H "Authorization: Bearer $PILOT_API_KEY" \
  -F "file=@launch.jpg"

URL imports require an operator-approved host, HTTPS, no redirects, and a file under 4 MiB. Send JSON with a url instead and we fetch it:

curl -X POST https://attentionpilot.com/api/v1/media \
  -H "Authorization: Bearer $PILOT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://cdn.example.com/launch.jpg"}'

Both return 201 with the stored file. filename, width, height and durationMs are optional on either path — send them if you already know them, skip them if you don't.

{
  "media": {
    "id": "9b2e…",
    "filename": "launch.jpg",
    "kind": "image",
    "mime": "image/jpeg",
    "size": 184320,
    "width": null, "height": null, "durationMs": null
  }
}

Post to every network

Attach media ids with media — the order you list them is the carousel order. 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 "Idempotency-Key: launch-post-001" \
  -H "Content-Type: application/json" \
  -d '{
    "caption": "We shipped per-network retries today.",
    "media": ["9b2e…"],
    "accounts": ["your-account-id"],
    "schedule": "draft"
  }'

On some networks media is not optional: Instagram and TikTok will not accept a text-only post at all, and YouTube needs a video. Target one of them without the right attachment and pre-flight rejects the request with a 422 naming the network — before anything is scheduled.

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", "linkedin"],
  "schedule": "2026-12-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": "linkedin", "status": "posted",
      "url": "https://www.linkedin.com/feed/update/urn:li:share:…" },
    { "platform": "x", "status": "failed",
      "error": "Account authorization was revoked during delivery." }
  ]
}

Errors worth handling