Write Post API

Schedule Post

Schedule a post by setting scheduled_at on create.

POST /api/v1/write-post/posts/ Live

There is no separate /schedule route. Scheduling uses Create Post with a future scheduled_at (ISO 8601). Timezone follows the account’s active workspace.

Authentication
Bearer API key required
Permission
write_post
Rate limit
Per-key default 60 req/min
Notes
  • Past scheduled_at values are rejected.
  • A dedicated POST /posts/{id}/schedule route is not implemented.
  • Post status will typically be scheduled until delivery runs.

Body fields

NameTypeRequiredDescription
headline string Yes Post headline (or title).
content string Yes Post body.
connection_ids array[integer] Yes Target connections.
scheduled_at string (ISO 8601) Yes Must be a future datetime. Example: 2026-12-01T15:30:00Z

Headers

HTTP
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Request body

JSON
{
  "headline": "Scheduled update",
  "content": "<p>Later today</p>",
  "connection_ids": [1],
  "scheduled_at": "2026-12-01T15:30:00Z"
}

Examples

cURL
curl -X POST "https://YOUR-DOMAIN/api/v1/write-post/posts/" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"headline":"Scheduled","content":"<p>Later</p>","connection_ids":[1],"scheduled_at":"2026-12-01T15:30:00Z"}'

Response example

JSON
{
  "success": true,
  "request_id": "req_...",
  "data": { "post": { "id": 2, "status": "scheduled" } }
}

Status codes

StatusMeaning
201Post scheduled
400Validation error (e.g. past scheduled_at)
401Invalid API key
403Missing write_post permission
429Rate limit exceeded

Try it

Paste your API key locally. It is sent only to this site’s API and is never saved.

Create API Key →

Errors

  • INVALID_API_KEY — missing/invalid Bearer token
  • SERVICE_ACCESS_DENIED — key lacks write_post
  • VALIDATION_ERROR — invalid payload or domain validation
  • RESOURCE_NOT_FOUND — unknown resource
  • RATE_LIMIT_EXCEEDED — too many requests

Full error reference →