Sessions API

Get a session

Read session state, outbound activity, and audit information.

GET/sessions/{bn_session_id}

Overview

Retrieve the current session projection and associated activity. Use this operation to reconcile webhook-driven state or investigate an interrupted workflow. The result is not a complete copy of the create-session request.

Before you start

The session must belong to the vendor associated with the API key. Use the returned BlueNotary session ID, not your notarization_id.

  1. Find the session ID

    Look up the BlueNotary ID associated with your order.

  2. Read current state

    Inspect session_doc and any stage information.

  3. Reconcile your system

    Apply the current state without repeating already-completed side effects.

Parameters

FieldRequirementDescription
bn_session_id
string · path
RequiredThe 24-character BlueNotary session identifier returned by Create Session.

Request example

Use a server-side API key. Replace example IDs and values before using this request in an approved test environment.

curl --request GET \
  --url 'https://app.bluenotary.us/api/integrationsv2/sessions/YOUR_SESSION_ID' \
  --header "Authorization: Bearer $BLUENOTARY_API_KEY"

Response

200 · Example success Illustrative values in the current response shape.

RESPONSE
{
  "session_doc": {
    "_id": "69a100000000000000001042",
    "status": "unsigned",
    "signingType": "ron",
    "notorizationType": "Acknowledgement",
    "createdAt": "2030-01-15T14:45:00.000Z",
    "updatedAt": "2030-01-15T14:45:00.000Z"
  },
  "all_outbound_vendor_logs": [],
  "audit_logs": []
}
  • session_doc.status, completion-processing markers, billing outcomes, and webhook event names are different concepts.
  • The optional session_completion_report contains a named Base64 report when available. Signed session PDFs use the separate signed-documents operation.
  • Staged eSign sessions may return current_stage and stages. A stage completion is not necessarily final session completion.
  • Use bounded reconciliation alongside webhooks. No universal polling interval is specified; choose a bounded schedule appropriate to the workflow and account limits.

Errors & recovery

StatusWhat happenedWhat to do
400Invalid session ID formatUse the exact returned bn_session_id.
401Authentication failedCheck the API key and its expiry.
403Session Not FoundConfirm the session exists, is not deleted, and belongs to this vendor.

Explore the response

Response simulator

LOCAL EXAMPLE

Explore the example response without an API key. This does not send requests or validate your account configuration.

This example uses the resource ID shown in the endpoint path.

Reading the response

Expect a resource-shaped response rather than a common success envelope.

  • session_doc: a selected set of session fields including status, signing type, timestamps, and payment-related information.
  • all_outbound_vendor_logs: recorded outbound activity for this session.
  • audit_logs: available audit entries. Treat participant information as sensitive.
  • session_completion_report: optional object with name, base64Doc, and initial_document_name.

Keep building