validation_failed
HTTP 400 — Request validation failed
validation_failed means the request's body, query or path failed validation, and the response usually lists each rejected field in its errors array.
What it means
The request body, query or path failed schema validation. The `errors` array usually lists each offending field as a JSON pointer with its own code and message; a few endpoints reject with a `detail` message and no `errors` array.
Common causes
- A required field is missing, the wrong type, or out of range.
- An unknown enum value (for example an event type or monitor type the API does not know).
How to fix it
Read the `errors` array and correct each named field. The API reference documents every request schema.
Should you retry?
No — the same payload will fail the same way.
The response shape
Every /v1 error is an RFC 9457 application/problem+json document: type links to this page, code is the stable value to branch on (never parse title or detail), and request_id identifies the request to support. Validation failures add an errors array of per-field JSON pointers.
API overview · API reference · All error codes:
missing_credentials— HTTP 401, Missing credentialsinvalid_api_key— HTTP 401, Invalid API keyinvalid_token— HTTP 401, Invalid access tokenunsupported_credential_type— HTTP 403, Credential type not usable on this surfaceinsufficient_scope— HTTP 403, Insufficient scopefeature_not_enabled— HTTP 403, Feature not enabled on this planresource_not_found— HTTP 404, Resource not foundrate_limited— HTTP 429, Rate limit exceededquota_exhausted— HTTP 429, Plan quota exhaustedidempotency_key_reused— HTTP 422, Idempotency-Key reused with a different requestidempotency_in_progress— HTTP 409, A request with this Idempotency-Key is still in progressinternal_error— HTTP 500, Internal server error