Status Codes
HTTP and JSON status meanings for the Postifys publishing API, including 202 media queue and success:false platform errors.
Quick answer: Interpret both HTTP status and the JSON
success/error.message fields. A 200/202 from Postifys does not guarantee every social network accepted the media.HTTP statuses you will see
| HTTP | Typical meaning in Postifys |
|---|---|
200 | Request handled; inspect JSON body for success and platform payload. |
202 | Accepted for async work (example: media queue). Poll status before publishing. |
302 | Browser redirect (auth/dashboard flows), not an API JSON success. |
401 | Missing/invalid API key or session. Recheck Authentication. |
403 | Authenticated but not allowed for that resource/account. |
404 | Unknown route or missing history/job id. |
413 | Payload/file too large for the current upload path. |
429 | Throttled (Postifys protections or upstream). Back off and retry. |
5xx | Server/provider failure. Check /health, Post History, and Errors. |
JSON success flags
{
"success": true,
"historyId": "post_...",
"data": { }
}{
"success": false,
"error": { "message": "Platform error details", "code": "META_PUBLISH_FAILED" }
}Known publish failure code families include Meta/YouTube/TikTok/Pinterest/LinkedIn publish failed markers and capacity codes such as disk guards. Always prefer the message text in Post History.