Invalid request (validation_error, invalid_request, invalid_cursor)

Symptom

The console shows that a field is not valid (usually next to the field), or «The requested page is no longer valid. The list was safely reset.» The API answers 422 validation_error (with field), 400 invalid_request, 400 invalid_idempotency_key, 413 payload_too_large or 422 invalid_cursor.

Cause

• A value outside the rules: length, format (email, UUID, SID, CIDR, https URL), numeric range or an unknown field.
• A malformed or oversized JSON body.
• A missing idempotency key, or one with invalid characters.
• A stale pagination cursor (the list changed or expired).

Fix

1. Read the message next to the indicated field and fix the value. The rules are in each view's article.
2. In an integration, use the response's field to know what to fix and check the request against the OpenAPI (unknown fields are refused).
3. For an invalid cursor, restart the list at the first page.
4. Large bodies: split the request (for example anchor imports of up to 500 lines).

When to escalate

If a value that meets the documented rules is refused, contact support with the field, the value (without secrets) and the time.