422 - Unprocessable Content
Description
The server understood the request and its syntax was valid, but it could not be processed because of a semantic issue with the request's content. Unlike a 400 Bad Request , which indicates malformed syntax, a 422 means the request is well-formed but conflicts with a business rule or a required condition was not met.
Common Scenarios
Idempotency-Key reused with a different payload : The Idempotency-Key header sent with this request was previously used for a request with a different request body. An Idempotency-Key must uniquely identify one specific operation and its exact payload; it cannot be reused for a different or new operation.
Field validation failure beyond basic syntax : A field is syntactically valid (e.g. a correctly formatted date or number) but fails a business rule, such as a date being in the past when a future date is required, or an amount being outside an allowed range.
Inconsistent combination of fields : Individual fields are valid on their own, but the combination submitted is not logically consistent (e.g. conflicting currency and amount fields, or a referenced resource that does not support the requested operation).
Missing conditionally required field : A field that is optional in general but required under specific circumstances (e.g. based on the value of another field) was not provided.
Resolution Steps
If this error was returned together with a reused Idempotency-Key : use a new , unique Idempotency-Key for any request that is genuinely different from a previous attempt (for example, retrying with a different payment method after a decline). Reusing the same key is only valid when resending the exact same request.
Review the detail field of the error response, which describes the specific semantic issue encountered.
Double-check the values and combinations of fields submitted against the endpoint's documentation, paying particular attention to any conditional requirements or business rules.
Confirm that any referenced resources (e.g. IDs of related objects) are in a state that supports the requested operation.
If the cause of the error is not clear from the response, contact support with the requestId from the error response and the exact time the request was sent.
Refer to the endpoint documentation for the specific validation rules and business constraints that apply to the request.