Starts a user action signing session, returning a challenge that will be used to verify the user’s intent to perform an action.
This is the first step of the User Action Signing flow.
CustomerEmployee)EndUser)Bearer Token: Used to authenticate API requests. More details how to generate the token: Authentication flows
The HTTP method that will be used to make the request that is being signed.
POST, PUT, DELETE, GET The path of the request that is being signed.
1The JSON-encoded body of the request that is being signed.
Optional indicator of which Dfns service being called.
Api Success
Challenge (string) to be signed by the requester with his private key.
A JWT that identifies the signing session.
Identifies the kind of credentials that can be used to sign the user action.
Value indicating if the user should be prompted for a second factor. Can be one of the following values:
required, preferred, discouraged Identifies the information needed to verify the user's signing certificate; can be one of the following:
none, indirect, direct, enterprise List of credentials that the user can use to sign the user action.
Optional url containing a secret value that can be used to enable cross device/origin signing.
Deprecated. Should not be used.