Wallets

GraphQL Endpoint

https://platform.beta.enjin.io/graphql

The Enjin Platform has one wallet-related mutation: CreateManagedWallet. Managed wallets are keypairs derived from the Wallet Daemon's seed plus an externalId you control — they let your application create signing accounts on demand without managing private keys.

For end-user wallets connected via WalletConnect, there's no mutation here — the user's wallet already exists on chain. To submit transactions signed by an end-user wallet, see CreateTransaction(..., signerAddress: <user-address>) followed by SignTransaction(uuid:, signedExtrinsic:) on the Transactions page.

CreateManagedWallet

Creates a new managed wallet keyed by your externalId. The wallet is the same keypair across networks (mainnet and canary) — there is no network / chain argument.

Once created, look up the wallet's public key with GetManagedWallet(externalId:) and use it as recipient on mint/transfer actions, or as signerAddress / signerExternalId on CreateTransaction to have it sign a transaction.

GraphQL
Response

mutation CreateManagedWallet {
  CreateManagedWallet(
    externalId: "e73f9f38-6832-4822-922b-b9225245ba24"
  )
}

{
  "data": {
    "CreateManagedWallet": true
  }
}

Looking for the signing flow?

For Wallet Daemon-signed transactions, see CreateTransaction.
For Managed Wallet-signed transactions, pass signerAddress or signerExternalId on CreateTransaction.
For end-user-signed transactions (WalletConnect, browser extension, etc.), pair CreateTransaction(... signerAddress:) with SignTransaction.

CreateManagedWallet​

CreateManagedWallet