Server — import a private key to create a WAAS wallet
Import a private key to create a waas account
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Request proof: a compact ES256 JWS, signed with the server's registered key, binding this request to a single-use nonce from GET /nonces. The JWS header is ServerSignerProofHeader and its payload is ServerSignerProofPayload. Required when the request carries a DYN API token and no JWT, and a server signer with a registered key controls the resource. A proof that is present is always verified.
4096^[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$Path Parameters
ID of the environment
36^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"95b11417-f18f-457f-8804-68e361f9164f"
Body
Import Private Key Request
EVM, MIDNIGHT, SVM, SUI, BTC, TON, STELLAR, TEMPO, ALEO, TRON List of client-side key generation identifiers
A base58 string with a max length of 100 characters
100^[1-9A-HJ-NP-Za-km-z]+$TWO_OF_TWO, TWO_OF_THREE, THREE_OF_FIVE Optional wallet ID of an existing legacy wallet being migrated
Protocol variant for the wallet. ed25519Standard = non-exportable Ed25519, used for raw-scalar import where the 32-byte input is the signing scalar itself (not an RFC-8032 seed). Omitted/ed25519Exportable = the default seed-based Ed25519. Only meaningful for ed25519 chains (e.g. Solana).
ed25519Exportable, ed25519Standard Response
Successfully created a room for wallet private key import ceremony. The response is text/event-stream (NOT JSON): clients consume it via EventSource.
The response is of type string.