Downloading Signed Documents
Once all signers have completed a document, you can download the signed PDF along with the audit trail. This guide covers manual downloads, automated retrieval, and archiving best practices.Download Endpoint
Retrieve a signed document using the download endpoint:
Response Headers
| Header | Description |
|---|---|
Content-Type | application/pdf |
Content-Disposition | attachment; filename="document-name.pdf" |
Content-Length | File size in bytes |
Download Options
Specify what to include in the download:Audit Trail / Certificate

Certificate Contents
| Information | Description |
|---|---|
| Document ID | Unique identifier for the document |
| Document Hash | SHA-256 hash of the original document |
| Signers | List of all signers with their roles |
| Signature Events | Timestamp, IP address, signature method for each signature |
| Verification | Cryptographic proof of document integrity |
Downloading the Certificate Separately
Storing Signed Documents
Download to Local Storage
Upload to Cloud Storage
Amazon S3
Google Cloud Storage
Automating Downloads with Webhooks
The most common pattern is to automatically download documents when they’re completed using webhooks.Webhook Handler
Python Webhook Handler
Archiving Best Practices
Download immediately on completion
Download immediately on completion
Set up a webhook handler to download documents as soon as they’re completed. This ensures you always have a copy, even if the document is later deleted from sajn.
Include the audit certificate
Include the audit certificate
Always download with
includeCertificate=true for legal purposes. The audit certificate provides proof of signing events.Use external IDs for organization
Use external IDs for organization
Set
externalId on documents to match your system’s identifiers. This makes it easy to organize and retrieve archived documents.Store metadata alongside PDFs
Store metadata alongside PDFs
Save document metadata (signers, dates, custom fields) alongside the PDF for easier searching and reporting.
Implement redundant storage
Implement redundant storage
Store signed documents in multiple locations (e.g., primary storage + backup) for disaster recovery.
Consider retention policies
Consider retention policies
Define how long to keep signed documents based on legal requirements. Some contracts may need to be retained for 7+ years.
Secure your archive
Secure your archive
Signed documents often contain sensitive information. Ensure your archive has appropriate access controls and encryption.
Error Handling
Document Not Ready
If the document isn’t completed yet:Document Not Found
Handling Errors
Next Steps
Webhooks
Set up automated document processing
Reminders & Expiration
Manage unsigned documents
API Reference
Download endpoint documentation
Creating Documents
Learn document creation basics

