Errors and retries
Errors use JSON:
{
"error": "Game is not connected to this workspace",
"code": "game_not_found"
}
| Status | Meaning | Retry? |
|---|---|---|
400 | Invalid JSON or field validation | No; fix the request |
401 | Missing, invalid, or revoked API key | No; replace credentials |
402 | Subscription inactive for new reports | No; restriction checks still work |
404 | Endpoint or connected game not found | No; verify URL and game ID |
413 | Request body too large | No; minimize the payload |
429 | Rate or monthly report limit reached | Retry only after the indicated operational limit resets |
500-599 | Temporary Guardyn/provider failure | Yes, with bounded exponential backoff |
Integrations should retry network errors, 429, and 5xx responses with a small capped backoff. Keep the same client_report_id while retrying a report.
Restriction checks must fail open after retries. Report submissions should tell the player Guardyn is unavailable and direct them to Roblox Report Abuse.