API
Errors & Partial Failures
Error format, status codes, and how partial publish failures are reported.
Error format
All errors share the same shape:
{ "error": { "code": "...", "message": "..." } }Status codes
| Status | Code | Meaning |
|---|---|---|
| 401 | UNAUTHENTICATED | Missing or invalid API key |
| 403 | BLOCKED | The account is blocked |
| 403 | PLAN_REQUIRED | Workspace is below the Creator plan |
| 404 | NOT_FOUND | Resource does not exist |
| 422 | VALIDATION_ERROR | Request body failed validation |
| 429 | RATE_LIMITED | Rate limit exceeded (30/min) |
| 500+ | INTERNAL_ERROR | Unexpected server error |
Partial failures
When you publish to multiple accounts, some may succeed while others fail. In that case the request returns HTTP 200 with a per-account breakdown:
{
"results": [
{ "accountId": "...", "status": "succeeded" },
{ "accountId": "...", "status": "failed", "error": "..." }
],
"summary": { "succeeded": 1, "failed": 1 }
}If every target fails, the request returns HTTP 502 instead.