Errors
Every failure has a canonical code and says whether to retry.
{
"error": {
"code": "SM_VALIDATION_FAILED",
"message": "The request is invalid.",
"retryable": false,
"requestId": "req_…",
"details": [
{ "path": "platforms.0.platformSpecificData.boardId", "code": "required", "message": "…" }
]
}
}Include requestId when you contact support. Retry only when retryable is true, after
Retry-After when it's present.
| Code | HTTP | Meaning |
|---|---|---|
SM_AUTH_MISSING, SM_AUTH_INVALID | 401 | No key, or not a valid one. |
SM_FORBIDDEN | 403 | The key lacks a scope, the IP isn't allowed, or a project policy forbids it. |
SM_NOT_FOUND | 404 | Not in this project. |
SM_VALIDATION_FAILED | 422 | The request is invalid; details says where. |
SM_CONFLICT | 409 | The resource changed or is in the wrong state. |
SM_IDEMPOTENCY_MISMATCH | 409 | The same key was used with a different request. |
SM_RATE_LIMITED | 429 | Too many requests for this key. |
SM_QUOTA_EXCEEDED | 429 | A plan limit was reached. |
SM_INSUFFICIENT_CREDITS | 402 | Not enough credits for these posts. |
SM_UNSUPPORTED_BY_PROVIDER | 422 | The platform's API doesn't offer this. |
SM_REQUIRES_PROVIDER_APPROVAL | 422 | The platform requires an approval we don't have yet. |
SM_ACCOUNT_REAUTH_REQUIRED | 422 | The account must be connected again. |
SM_ACCOUNT_PERMISSION_MISSING | 422 | The user didn't grant a permission this needs. |
SM_MEDIA_INVALID | 422 | A file the platform won't take. |
SM_MEDIA_NOT_READY | 409 | Media still processing. |
SM_MESSAGING_WINDOW_CLOSED | 422 | The platform's reply window for this conversation has passed. |
SM_TEMPORARILY_UNAVAILABLE | 503 | Try again shortly. |
SM_INTERNAL | 500 | Our failure. |
Per-account publish results use these too, plus SM_PROVIDER_RATE_LIMITED,
SM_PROVIDER_UNAVAILABLE, SM_PROVIDER_REJECTED, SM_PROVIDER_DUPLICATE and
SM_OUTCOME_UNKNOWN (the platform didn't say; SociaMesh checks before any retry). The platform's
own code is in providerCode.