Notarize with the BlueNotary network

Confirm network routing

This flow leaves the notary unassigned in the create request. The account determines the candidate pool and when dispatch begins.

• Network routing is enabled for this account.
• Open calls are permitted, and the intended automatic-dispatch trigger is configured.
• Signer invitation settings match your delivery plan.
• Documents are ready before participants begin signing.

Create the session

Send notarize_now, omit session_notary_email, and provide the signers. Add your prepared document payload through session_documents.

{
  "notarization_id": "order-1042",
  "signing_type": "ron",
  "session_type": "gnw",
  "notarization_timing_type": "notarize_now",
  "all_signers": [
    {
      "first_name": "Sam",
      "last_name": "Signer",
      "email": "sam@example.com"
    }
  ]
}

What happens next

Treat creation, dispatch, acceptance, and signing as separate stages. Their exact timing depends on the account and participant actions.

1. Create

   Store bn_session_id and the returned participant links.

2. Dispatch

   The configured trigger attempts an open call to eligible notaries.

3. Acceptance

   Observe open_call_accepted for assignment progress.

4. Sign and complete

   Follow session events and retrieve final documents after processing.

Deliver participant access

Use the account’s RON email policy or distribute returned links through your application. The eSign field send_signer_emails is not established as a RON invitation override.

• Map normal separate-device RON links by signer_index.
• Do not expose one participant’s link to another.
• Use a preparation hold when document work must finish before invitations.

If no notary is assigned

Check the session state, account routing, disabling gates, preparation status, and whether the configured trigger actually ran. Creating another session is not a reliable way to retry dispatch.

Receive the outcome

Subscribe to session completion and termination events. Retrieve PDFs through /signed_documents, or choose the appropriate webhook document mode. Retain the session ID for support and reconciliation.

Keep building