You’re viewing Porto developer documentation — a distinct product from Anchorage Digital’s core custody platform. Go to Anchorage Digital docs →
Api-Access-Key header. Sensitive operations—including transfers, withdrawals, and trusted-destination management—additionally require an Ed25519 request signature, supplied in the Api-Signature and Api-Timestamp headers and generated from your private key over the canonical request.
Base URLs
Child control keys for self-custody
Self-custody organizations send one additional header when initiating transfers through the API:Api-Child-Control-Key. It carries the source wallet’s child control key as 64 lowercase hex characters, derived locally from your Master Control Key. Anchorage Digital’s hardware security modules cannot decrypt a self-custody wallet’s signing keys without it, and the Master Control Key itself is never sent. Derive the value fresh for each transfer using the wallet’s derivationPath; see Generating child control keys for the derivation recipe and reference code.
For the exact signing recipe and code samples, see Signing requests. For how authentication, keys, and permission groups fit together, see Setting up.