Wallet API helps developers to create and manage Kaia accounts and send transactions. It provides a wallet for secure storage of your Kaia account private keys as well. The functionality of the multiple endpoints enables you to do the following actions:

• manage accounts
  • create, retrieve and delete Kaia accounts
  • update Kaia accounts to multisig accounts, role-based accounts, etc.
  • manage private keys of all accounts registered on the account pools
  • manage account pools
• create and send transactions
  • basic transaction
  • fee delegation transaction
    • global fee delegation transaction
    • user fee delegation transaction
  • multisig transaction
  • RLP-encoded transaction

Basic transaction on KAS is the same as Kaia transaction, and fee delegation transaction divides its type depends on who pays the transaction fee. With the Global Fee Delegation transaction scheme, the transaction fee will initially be paid by GroundX and then be charged to you at a later date. With the User Fee Delegation transaction scheme, you create an account that pays the transaction fees on behalf of the users for a transaction. Multisig transaction needs more than one signature for transaction transfer. In the case of multisig accounts, a transaction will automatically be sent to Kaia once (Threshold) is met.

The administrator can use account management features to create or retrieve account pools on KAS Console.

IMPORTANT

Wallet API v2 does not support some features. Make sure to check prior to using the API.

[Not support]

• Service Chain
• Account management for external custodial keys
• Multi-signature for RLP-encoded transaction

Managed Nonce

• If the nonce is 0 when sending requests to endpoints in the format /v2/tx/*, Wallet API will automatically parse the nonce of this account to set the transaction parameters.

CAUTION

In the event of an overload, the order of transaction and nonce cannot be guaranteed. For example, if the transaction that was supposed to be executed first turns out to have a bigger nonce, it may have to wait before the transactions with lower nonces go through.

In cases when order matters, you can set the nonce yourself. The transaction parameters will be set with the data provided by you.

A common error titled Unauthorized occurs regardless of API type if you have authorization issues.

401: Unauthorized