/📚 Guides/Error Handling

Error Handling

All errors follow a consistent JSON shape so you can handle them programmatically.

Error shape

{
  "error": {
    "code": "invalid_request",
    "message": "scheduled_at must be in the future",
    "param": "scheduled_at",
    "request_id": "req_9x8y7z"
  }
}

Status codes

Code	Meaning
400	Invalid request — check the `param` field.
401	Missing or invalid API key.
403	API key lacks the required scope.
404	Resource not found in this workspace.
409	Conflict — e.g. deleting a published post.
429	Rate limit exceeded.
5xx	Transient — retry with exponential backoff.

Always log the request_id — it's the fastest way for support to trace a failure.

Guides → Scheduling Logic

Continue →