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

The client requires a valid authToken. See Required headers for details on obtaining tokens.

KeySigner configuration

The KeySigner class provides factory methods for each supported key type. Each method takes a credential ID and the private key bytes:
If you have a PEM file, strip the header/footer lines and Base64-decode the content to get the DER bytes.

Sync vs async clients

The SDK provides both synchronous and asynchronous clients:

Available API domains

The client provides typed access to all DFNS API domains:

Error handling

Last modified on July 7, 2026