Activate Wallet
Activates a wallet by deploying the account contract on-chain, making it ready for transactions.
This operation is required for wallets on networks where you need to explicitly activate your account on-chain before it can be used for transactions.
- Starknet: Deploys the account contract using the wallet’s public key to initialize the account on the blockchain. No additional parameters required.
- Concordium: Deploys the account using credential deployment information and cryptographic randomness returned by the IDApp.
- Canton: Registers the wallet on a validator. You must specify the
validatorIdto activate the wallet. Before activation, the wallet cannot be used and its address will not have a prefix.
Authentication
✅ Organization User (CustomerEmployee)✅ Delegated User (
EndUser)✅ Service Account
Required Permissions
Wallets:Create: Always required.Authorizations
Bearer Token: Used to authenticate API requests. More details how to generate the token: Authentication flows
User Action Signature: Used to sign the change-inducing API requests. More details how to generate the token: User Action Signing flows
Path Parameters
Wallet id.
1 - 64Body
- Option 1
- Option 2
- Option 3
Starknet: No parameters required.
Response
Success
Transaction id.
1 - 64^tx-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"tx-583hu-sp2p7-slvb9nqpa3hd8bus"
Wallet id.
1 - 64^wa-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"wa-5pfuu-9euek-h0odgb6snva8ph3k"
Algorand, AlgorandTestnet, Aptos, AptosTestnet, ArbitrumOne, ArbitrumSepolia, Arc, ArcTestnet, Areum, AvalancheC, AvalancheCFuji, Base, BaseSepolia, Berachain, BerachainBepolia, Bitcoin, BitcoinSignet, BitcoinTestnet4, BitcoinCash, Bob, BobSepolia, Bsc, BscTestnet, Canton, CantonTestnet, Cardano, CardanoPreprod, Concordium, ConcordiumTestnet, Celo, CeloAlfajores, Codex, CodexSepolia, CosmosHub4, CosmosIcsTestnet, Dogecoin, DogecoinTestnet, Ethereum, EthereumClassic, EthereumClassicMordor, EthereumSepolia, EthereumHoodi, FlareC, FlareCCoston2, FlowEvm, FlowEvmTestnet, Hedera, HederaTestnet, Ink, InkSepolia, InternetComputer, Ion, IonTestnet, Iota, IotaTestnet, Kusama, KusamaAssetHub, Litecoin, LitecoinTestnet, Movement, MovementTestnet, Near, NearTestnet, Optimism, OptimismSepolia, Origyn, Plasma, PlasmaTestnet, Plume, PlumeSepolia, Paseo, PaseoAssetHub, Polkadot, PolkadotAssetHub, Polygon, PolygonAmoy, Polymesh, PolymeshTestnet, Rayls, RaylsTestnet, Robinhood, RobinhoodSepolia, SeiAtlantic2, SeiPacific1, Solana, SolanaDevnet, Sonic, SonicTestnet, Starknet, StarknetSepolia, Stellar, StellarTestnet, Sui, SuiTestnet, Tezos, TezosShadownet, Tempo, TempoModerato, Tsc, TscTestnet1, Ton, TonTestnet, Tron, TronNile, Westend, WestendAssetHub, Xdc, XdcApothem, XLayer, XLayerSepolia, XrpLedger, XrpLedgerTestnet The user who initiated the request.
Signs an unsigned transaction and broadcasts it to chain. This is the recommended transaction kind for EVM networks — use it instead of the deprecated Evm and Eip1559 kinds. It accepts a JSON transaction object (type 0 legacy, 2 EIP-1559, or 4 EIP-7702) as well as a hex-encoded raw transaction.
For EVM transactions, you may use JSON objects:
For Starknet transactions, you may use invocation request objects (https://github.com/starkware-libs/starknet-specs/blob/v0.8.1/api/starknet_api_openrpc.json#L2621):
For Concordium transactions, you may use JSON objects (from https://github.com/Concordium/concordium-node-sdk-js/blob/sdk/12.0.0-alpha.3/packages/sdk/src/transactions/Transaction.ts#L102)
- Transaction
- PSBT
- SignDocDirect
- EVM Sponsored transaction
- Function Call
- Canton Transfer Preapproval
- <Deprecated> EVM Transaction
- <Deprecated> EVM EIP-1559
- Create Solana Nonce Accounts
- AcceptInboundAsset
- Solana CCTP Burn
- Offer Settlement
- Account Activation
- Transaction Cancellation
- Transaction Speed Up
Pending, Executing, Broadcasted, Confirmed, Failed, Rejected 1 - 64^ap-[a-z0-9]{5}-[a-z0-9]{5}-[a-z0-9]{14,16}$"ap-2a9in-tt2a1-983lho480p35ejd0"
The id of the replacement transaction (cancel or speed-up) issued for this transaction.
Structured representation of the data used to construct the signature (e.g. nonce, gas parameters). Shape is blockchain specific.