(Coming Soon)
Idempotency errors
When the Idempotency-Key
header is used, BlueSnap may return one of the following errors:
Code | Name | Description |
---|---|---|
60101 | SAME_IDEMPOTENCY_KEY_WAS_ALREADY_IN_USE_WITH_PREVIOUS_DIFFERENT_REQUEST | This occurs if there is an attempt to reuse an Idempotency-Key with a request different from the first request attempt. BlueSnap will respond with HTTP 422 status code [Unprocessable Entity]. |
60102 | REQUEST_WITH_SAME_IDEMPOTENCY_KEY_ALREADY_IN_PROGRESS. | This occurs if a request is retried using the same Idempotency-Key as the original request while it is still being processed. BlueSnap will respond with HTTP 409 status code [Conflict]. |
60103 | IDEMPOTENCY_KEY_MAX_LENGTH_LIMIT_EXCEEDED | This occurs if the Idempotency-Key header exceeds the maximum length of 64 characters. |
60104 | INVALID_IDEMPOTENCY_KEY | This occurs if the Idempotency-Key header contains invalid characters. It can only contain Alpha-Numeric characters or hyphens. |
For more information about idempotency, refer to Idempotency (Coming Soon).