Signers, witnesses, and shared devices

Add the signers

Provide all_signers as an array. For a normal RON signer, include first_name, last_name, and email. eSign also requires an action. Preserve your own participant mapping alongside the returned links.

{
  "all_signers": [
    {
      "first_name": "Sam",
      "last_name": "Signer",
      "email": "sam@example.com"
    },
    {
      "first_name": "Taylor",
      "last_name": "Signer",
      "email": "taylor@example.com"
    }
  ]
}

Match each signing link

For ordinary separate-device RON, signer_index identifies the signer associated with a signing_urls entry. Never share a participant’s personalized link with another person.

• Keep link distribution inside your application’s access checks.
• Do not log the full URL.
• Treat IPEN and shared-device responses separately.
• Preserve the API’s legacy witnessess_signing_urls field spelling when parsing.

Choose invited or network witnesses

Use your own invited witnesses or request BlueNotary-sourced witnesses. Confirm identity requirements for the chosen workflow.

Enable shared-device RON

Set same_device_signing_mode to all under session_configurations. Optionally designate one signer as the host with is_shared_device_owner; the first signer is the default RON host.

• Only one shared-device owner can be selected.
• Test the actual host-led participant sequence.
• Shared-device eSign uses different access behavior and should have its own acceptance test.

{
  "session_configurations": {
    "same_device_signing_mode": "all"
  },
  "all_signers": [
    {
      "first_name": "Sam",
      "last_name": "Signer",
      "email": "sam@example.com",
      "is_shared_device_owner": true
    },
    {
      "first_name": "Taylor",
      "last_name": "Signer",
      "email": "taylor@example.com"
    }
  ]
}

Use an approved identity workflow

Per-signer authentication_type accepts kba, biometrics, or skip in the input mapping. Choose only the method approved and supported for the account, product, and participant.

• Per-signer overrides can take precedence over defaults.
• A session-level customer authentication option applies to the primary signer, not every participant.
• Avoid unrecognized values; accepted input does not necessarily mean a valid workflow.

Handle participant changes deliberately

API v2 does not provide a general participant add/remove endpoint. If participants change after creation, follow the supported session UI/process and observe relevant invitation events.

Keep building