BVNK Ledger — Self-Custody Key Management
Key management endpoints for self-custody wallets.
How it works
A self-custody wallet is derived from an HD master key (a BIP39 seed phrase) that BVNK holds inside a hardware vault enclave. There is exactly one master key per Embedded Partner Customer (EPC), and every self-custody wallet that EPC holds, on every network, derives its address from that one key via a BIP44 derivation path. This is why key pairs are modelled as their own resource rather than nested under a wallet.
Data transit key
The data transit key is the RSA public key that client-side encryption wraps against for operations that move key material (such as key export and import). It is tenant-wide and long-lived: fetch it once and reuse it.
Authentication
Requests authenticate as the Embedded Partner, not as the end customer. The EPC has no BVNK credentials in this release.
Authentication
- OAuth 2.0: oauth2ClientCredentials
Standard BVNK API credentials.
Security Scheme Type: | oauth2 |
|---|---|
OAuth Flow (clientCredentials): | Token URL: https://api.bvnk.com/oauth/token Scopes:
|
Contact
BVNK: