Skip to content

key_refused

The API answers key_refused in the code field of its error envelope.

  • HTTP status: 422 Unprocessable Content.
  • Fault: customer. Something in the request, or on your side (a credential, a setting, the data), needs to change before it can succeed.

The destination did not accept the pending key, so nothing was switched and the current key keeps working. Check that the user’s RSA_PUBLIC_KEY_2 holds the new public key.

Every error carries code, message (for your logs, in English), fault, request_id and docs (this page). Quote the request_id when you ask about a particular request. See all error codes.