April 24, 2026 · Cerebras
Cerebras Inference validation errors now return HTTP 400 instead of 422
API requests that fail validation now return HTTP 400 Bad Request instead of 422 Unprocessable Entity, aligning the HTTP status code with standard behavior across major inference providers. This applies to all validation errors, including missing required fields, malformed request bodies, and unsupported parameters. The error response body schema is unchanged.
SDK impact
If you use the Cerebras or OpenAI Python or Node.js SDK, validation errors now raise BadRequestError instead of UnprocessableEntityError. Both SDKs map HTTP status codes to distinct exception classes.
| | Before | After | | - | - | - | | HTTP status code | 422 | 400 | | Python exception | UnprocessableEntityError | BadRequestError | | Node.js error name | UnprocessableEntityError | BadRequestError |
Action required
- If your code handles
UnprocessableEntityErrorby name or checks for status code422, update toBadRequestErroror400. - If you use raw HTTP and branch on the status code, update
422to400. - No changes are needed if your error handling catches the base class (
APIStatusErrororAPIError).
Latest Cerebras Inference changes
Kimi K3.1 Pro added to Dedicated catalog, with image inputs and reasoning levels
Kimi K3, GLM 5.3 Flash and three more models added to Dedicated catalog
Service Tiers docs updated for service_tier reporting and auto and priority fallbacks
qwen-3.8-27b Developer tier rate limit raised temporarily to 750K tokens per minute
gemma-4-31b removed from Cerebras public endpoints, still on Dedicated