A PUT request sent to unfreeze a card.
For a previously frozen card, you can unfreeze it to allow new transactions.
Be aware than even after a successful unfreeze, the card may remain in the frozen status for compliance reasons. The frozenBy field will indicate if this is the case.
The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).
Although the HTTP standard specifies "unauthorized", semantically this response means "unauthenticated". That is, the client must authenticate itself to get the requested response.
The client does not have access rights to the content; that is, it is unauthorized, so the server is refusing to give the requested resource. Unlike 401 Unauthorized, the client's identity is known to the server.
The request was well-formed but was unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time ("rate limiting").
The server has encountered a situation it does not know how to handle.