A POST request sent to create a wallet.
Separate wallet creation is only supported for B2B distributors.
Consumer wallets are created as a part of user creation API call.
Info
When creating a wallet, you must provide either the
addressproperty (for debit accounts) or thewithdrawalAddressproperty (for prepaid accounts), depending on the type of wallet you are creating.
Info
Whenever a non custodial wallet address is provided to this endpoint, the client will have to verify the wallet ownership with the
/wallets/:id/verifyendpoint.
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 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.
This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response.
The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.
This error response is given when the server is acting as a gateway and cannot get a response in time.