Get signed documents

Overview

Read the session’s final-document records. Decode the Base64 contents and persist the required artifacts in your own authorized storage. This endpoint is separate from the short-lived document links available through webhook delivery.

1. Observe readiness

   Use the final completion workflow and reconcile status if necessary.

2. Fetch the files

   Call signed_documents with the stored BlueNotary ID.

3. Decode and persist

   Store the PDFs with their original-document mapping and access controls.

Parameters

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/signed_documents' \
  --header "Authorization: Bearer $BLUENOTARY_API_KEY"

Response

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

{
  "final_documents": [
    {
      "name": "signed-agreement.pdf",
      "base64Doc": "BASE64_PDF_CONTENT",
      "initial_document_name": "agreement.pdf"
    }
  ]
}

• An HTTP 200 response with final_documents: [] can mean the final files are not ready yet; it is not a transport failure.
• The endpoint returns Base64 file content, not a universal array of download URLs.
• Completion reports and audit history are available through their separate response locations in Get Session.
• The sample Base64 is a placeholder. In production, validate and securely store decoded bytes.

Errors & recovery

Explore the response

File response fields

Each object in final_documents describes a final file.

• name: final output name.
• base64Doc: encoded PDF bytes.
• initial_document_name: name of the source document used to associate the output.
• Webhook links instead use document_url and document_url_expires_at; those are not fields in this response example.

Keep building