List of Clatter Labs API error codes

ReferenceUpdated November 2, 2026

Status	Codes
400	`bad_request`; Model API: `invalid_request`, `invalid_json`, `unsupported_content`, `unsupported_parameter`, `invalid_effort`
401	`invalid_api_key`, `missing_account_id`, `account_mismatch`; Model API also `expired_api_key`
402	`out_of_credits`
403	`insufficient_scope`, `early_access`, `no_cloud_account`, `account_suspended`, `team_scope_denied`
404	`not_found`; Model API: `model_not_found`, `not_supported`
405	`method_not_allowed`
410	`model_retired`
413	`too_large`; Model API: `request_too_large`
429	`rate_limited`, `too_many_runs`, `window_limit_reached`, `weekly_limit_reached`, `monthly_limit_reached`, `team_daily_quota_reached`, `team_spend_limit_reached`
502 / 503 / 504	`upstream`, `unavailable`; Model API: `model_overloaded`, `model_unavailable`, `model_timeout`, `empty_response`, `stream_error`

Code Buckets also uses 402 quota_exceeded and 402 storage_full. Search this Help Center for any code.

Good to know#

On 429, wait the Retry-After seconds before retrying.
Every API request sends your key and your Account ID (X-Clatter-Account: CL-…); a key alone is refused.
A new key's secret is shown only once. Clatter Labs stores only a hash, so a lost key can't be recovered.

General support: support@clatterlabs.com or team@clatterlabs.xyz
Infrastructure questions, or permanent deletion of your data (your whole account or one service): infrastructure@clatterlabs.xyz

We usually reply within the first hour, and always within 24 hours. A full support team is with you.

Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.

General support

Infrastructure questions, or permanent deletion of your data

For deleting your whole account or the data of one service.