Through this endpoint users can easily create a new Master Wallet through the API. The user provides the desired Wallet name and in return the response includes the walletId
. That new Wallet can be additionally also backed up through the Crypto APIs Dashboard.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Defines the name of the wallet that will be generated.
Represents if the generated wallet is only for mainnet or only for testnet .
Specifies the version of the API that incorporates this endpoint.
Defines the ID of the request. The requestId
is generated by Crypto APIs and it's unique for every request.
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error. context
is specified by the user.
Represents the sender's specific and unique Wallet ID of the sender.
API Key
{
"context": "yourExampleString",
"data": {
"item": {
"walletName": "yourWalletName",
"walletType": "test"
}
}
}
{
"apiVersion": "2023-04-25",
"requestId": "601c1710034ed6d407996b30",
"context": "yourExampleString",
"data": {
"item": {
"walletId": "62b9b5c3b97f4b0108092716"
}
}
}