King Push API v1
Automate scheduling, publishing and Bolt from your own code. Create a key in your dashboard, then send it with every request.
Authentication
Keys carry your plan's entitlements and count against your 120 req/min limit.
curl https://kingpush.app/api/v1/me -H "Authorization: Bearer kp_live_YOUR_KEY"
Endpoints
| Method | Path | What it does |
|---|---|---|
| GET | /api/v1/me | Your profile, plan, trial and entitlements |
| GET | /api/v1/posts | All your posts with per-account publish receipts |
| GET | /api/v1/posts/:id | One post + delivery status |
| POST | /api/v1/posts | Publish now or schedule — { title, accounts: [], publishNow, scheduledAt }. Plan caps enforced automatically. |
| GET | /api/v1/social/accounts | Connected social accounts available as destinations |
| POST | /api/v1/ai/chat | Bolt copilot — { message } returns plans and answers |
Schedule a post on all your accounts
# 1. list your linked accounts
curl https://kingpush.app/api/v1/social/accounts -H "Authorization: Bearer kp_live_YOUR_KEY"
# 2. schedule to two of them
curl -X POST https://kingpush.app/api/v1/posts -H "Authorization: Bearer kp_live_YOUR_KEY" -H "Content-Type: application/json" -d '{
"title": "Going live tonight at 8 — bring snacks",
"scheduledAt": "2026-10-01T18:00:00Z",
"accounts": ["sa_xxxx", "sa_yyyy"]
}'
# 3. publish immediately instead: add "publishNow": true and drop scheduledAt
Errors & limits
Errors come back as { "error": "message", "upgrade": true? } with proper status codes (401 bad key, 403 plan cap, 429 rate limit). Revoke a key in your dashboard and it dies instantly.