validation_failed

What it means

The request body, query or path failed schema validation. The `errors` array lists each offending field as a JSON pointer with its own code and message.

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 credentials
• invalid_api_key — HTTP 401, Invalid API key
• invalid_token — HTTP 401, Invalid access token
• unsupported_credential_type — HTTP 403, Credential type not usable on this surface
• insufficient_scope — HTTP 403, Insufficient scope
• feature_not_enabled — HTTP 403, Feature not enabled on this plan
• resource_not_found — HTTP 404, Resource not found
• rate_limited — HTTP 429, Rate limit exceeded
• quota_exhausted — HTTP 429, Plan quota exhausted
• idempotency_key_reused — HTTP 422, Idempotency-Key reused with a different request
• idempotency_in_progress — HTTP 409, A request with this Idempotency-Key is still in progress
• internal_error — HTTP 500, Internal server error