Enums | |
---|---|
UNKNOWN_ERROR_RESPONSE_CODE |
Do not ever set this default value! |
INVALID_API_VERSION |
Used if the request's API version is unsupported. Analogous to HTTP error 400 |
INVALID_PAYLOAD_SIGNATURE |
Used if the signature of the payload is to an unknown or inactive key. Analogous to HTTP error 401 |
INVALID_PAYLOAD_ENCRYPTION |
Used if the encryption of the payload is to an unknown or inactive key. Analogous to HTTP error 400 |
REQUEST_TIMESTAMP_OUT_OF_RANGE |
Used if the requestTimestamp is not ± 60s of now. Analogous to HTTP error 400 |
INVALID_IDENTIFIER |
Used if an identifier sent in the request was invalid or unknown. This may include PIAID, captureRequestId, Google Payment Token, etc. The type of the invalid identifier should be specified in the errorDescription. Analogous to HTTP error 404 |
IDEMPOTENCY_VIOLATION |
Used if the request violates the idempotency requirements for the request. Analogous to HTTP error 412 |
INVALID_FIELD_VALUE |
Used if the request contains a value for a field that isn't in the set of supported values. Analogous to HTTP error 400 |
MISSING_REQUIRED_FIELD |
Used if a field that is required is unset in the request. Analogous to HTTP error 400 |
PRECONDITION_VIOLATION |
Used if a constraint on the operation is violated (e.g. when a request for a refund amount exceeds the amount remaining on the transaction). Analogous to HTTP error 400 |
USER_ACTION_IN_PROGRESS |
Used if the request cannot be processed at this time because it would interrupt an in-process user action which effectively acts as a system lock. This code must not be used to indicate failures due to implementation-specific internal concurrency errors. Analogous to HTTP error 423 |
INVALID_DECRYPTED_REQUEST |
Used if the request payload could be decrypted, but the resulting message could not be parsed. Analogous to HTTP error 400 |
FORBIDDEN |
Access to the requested resource is foribidden. Analogous to HTTP error 403 |
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-16 UTC.
[null,null,["Last updated 2024-10-16 UTC."],[[["This documentation outlines error response codes for API requests, providing specific codes for various error scenarios."],["Each error code corresponds to a specific issue, such as invalid API version, payload issues, timestamp discrepancies, or identifier problems."],["These codes align with standard HTTP error codes (e.g., 400, 401, 403, 404) for easy understanding and integration."],["The `errorDescription` field provides additional context about the specific identifier or issue causing the error."],["Developers should avoid using the `UNKNOWN_ERROR_RESPONSE_CODE` and instead select the most appropriate specific error code."]]],[]]