Skip to main content

Request signing

All state-changing requests made to the DFNS API must be cryptographically signed. The SDK handles this automatically when you configure a signer.
For a detailed explanation of request signing and User Action Challenges, see Signing requests.

Authentication tokens

Both DfnsClient and DfnsDelegatedClient require a valid auth_token. See Required headers for details on obtaining tokens.

KeySigner configuration

The KeySigner signs challenges using your private key. It supports Ed25519, ECDSA (secp256k1, P-256), and RSA keys.

Available API domains

Both clients provide typed access to all DFNS API domains:

Delegated signing

For implementing delegated signing flows (user passkeys or external KMS), see:
Last modified on July 7, 2026