---
title: "Download Signed Document Audit Trails via BoldSign API"
description: "Learn to download tamper-evident audit trail PDFs for signed documents using BoldSign API, with endpoint details, auth headers, SDK examples, & compliance tips."
url: "https://boldsign.com/blogs/audit-trails-download-api-boldsign/"
---

1. [Blog](https://boldsign.com/blogs.md)
2. [API](https://boldsign.com/category/api.md)

# How to Download an Audit Trail PDF Using the BoldSign API

[Ranjitha Vazhivittan](https://boldsign.com/author/ranjitha-vazhivittan/) February 17, 2026 Updated April 10, 2026 4 min read

> **TL;DR:** Download BoldSign audit trail PDFs (signer, timestamps, IPs, events) via `GET /v1/document/downloadAuditLog` using `documentId`.

When documents are signed, you need proof, not just signatures. Audit trails provide tamper-evident evidence of who signed, when, and from where. In this guide, you’ll learn how to download audit trail PDFs programmatically using the BoldSign API.

## Why would you use BoldSign audit trails

In BoldSign, an audit trail helps you:

- Protect documents with a verified [signing history](https://developers.boldsign.com/how-to-guides/retrieve-esignature-document-history)
- Confirm signer identities and time stamps
- Reduce legal risk with tamper-evident evidence
- Support legal compliance by storing accurate records
- Improve transparency by capturing each signing event

## When does audit trail management matter most

Audit trails are especially critical when:

- Multiple departments handle contracts with vendors, clients, or employees
- Legal teams require a verified signing history for disputes
- Compliance audits demand proof of document integrity
- Organizations must store tamper-evident audit trail records alongside signed documents

## What you’ll need before calling the audit trail API

Make sure you have:

- A [BoldSign account](https://account.boldsign.com/signup?planId=1076\&utm_source=boldsignblogs\&utm_medium=redirect\&utm_campaign=boldsign) (sandbox or production)
- An [API key](https://developers.boldsign.com/authentication/api-key) (or [OAuth2 access token](https://developers.boldsign.com/authentication/oauth-2-0)) to call BoldSign APIs over HTTPS
- A REST client such as curl, Postman, or your preferred HTTP library
- The  `documentId` of the signed document
- The `onBehalfOf`  email address if the document was sent on behalf of another person *(Optional)*

For more details refer to [API documentation](https://developers.boldsign.com/documents/download-audit-trail).

**Authentication headers**

Use one of the following:

- **API Key:** X-API-KEY: \<your key>
- **OAuth2:** Authorization: Bearer \<access_token>

## Which endpoint do you use to download audit trails

You use the same endpoint for both regular and on-behalf signature requests.

| | | | |
| - | - | - | - |
| **Task**  | **Method + path**  | **Required inputs**  | **Output**  |
| Download audit trail (regular document)  | GET /v1/document/downloadAuditLog  | `documentId` | Audit trail PDF  |
| Download audit trail (on-behalf document)  | GET /v1/document/downloadAuditLog  | `documentId`, `onBehalfOf `  | Audit trail PDF  |

## Step-by-step: How to download an audit trail for a regular document

**Required query parameter:**

- `documentId`: The unique identifier of the signed document.

```
curl -X GET \
  'https://api.boldsign.com/v1/document/downloadAuditLog?documentId={Your document Id}' \
  -H 'accept: application/pdf' \
  -H 'X-API-KEY: {your-api-key}'
```

```
var apiClient = new ApiClient("https://api.boldsign.com", "Your API-KEY");
var documentClient = new DocumentClient(apiClient);
var documentStream = documentClient.DownloadAuditLog("YOUR_DOCUMENT_ID");
```

```
import boldsign

configuration = boldsign.Configuration(api_key="YOUR_API_KEY")

with boldsign.ApiClient(configuration) as api_client:

    document_api = boldsign.DocumentApi(api_client)
document_stream = document_api.download_audit_log(document_id="YOUR_DOCUMENT_ID")
```

```
<?php require_once "vendor/autoload.php";
use BoldSign\Configuration;
use BoldSign\Api\DocumentApi;

$config = new Configuration();
$config->setApiKey('YOUR_API_KEY');

$documentApi = new DocumentApi($config);
$document_stream = $documentApi->downloadAuditLog($document_id = 'YOUR_DOCUMENT_ID');
```

```
ApiClient client = Configuration.getDefaultApiClient();
client.setApiKey("YOUR_API_KEY");
DocumentApi documentApi = new DocumentApi(client);
File documentStream = documentApi.downloadAuditLog("YOUR_DOCUMENT_ID", null);
```

```
import { DocumentApi } from "boldsign";

const documentApi = new DocumentApi();
documentApi.setApiKey("YOUR_API_KEY");

const documentStream = documentApi.downloadAuditLog("YOUR_DOCUMENT_ID");
```

## Step-by-step: How to download an audit trail for documents sent on behalf of others

**Required query parameters:**

- `documentId`: The unique identifier of the signed document.
- `onBehalfOf`: The email address of the sender on whose behalf you’re acting.

Use `onBehalfOf` only if the document was sent on behalf of someone else.

> **Tip:** If `onBehalfOf` contains special characters such as + or spaces, make sure it is URL encoded.

When a document is sent by you on behalf of another person, the download audit trail operation can still be performed from your account by specifying that person’s email address in the `onBehalfOf` field. This ensures you can access the audit trail even if the document wasn’t directly sent from your own address.

```
curl -X GET \
  'https://api.boldsign.com/v1/document/downloadAuditLog?documentId=YOUR_DOCUMENT_ID&onBehalfOf=ON_BEHALF_EMAIL' \
  -H 'accept: application/pdf' \
  -H 'X-API-KEY: {your-api-key}'
```

```
var apiClient = new ApiClient("https://api.boldsign.com", "Your API-KEY");
var documentClient = new DocumentClient(apiClient);
var documentStream = documentClient.DownloadAuditLog("YOUR_DOCUMENT_ID", "ON_BEHALF_EMAIL");
```

```
import boldsign

configuration = boldsign.Configuration(api_key="YOUR_API_KEY")

with boldsign.ApiClient(configuration) as api_client:

    document_api = boldsign.DocumentApi(api_client)
document_stream = document_api.download_audit_log(
    document_id="YOUR_DOCUMENT_ID", on_behalf_of="ON_BEHALF_EMAIL"
)
```

```
<?php require_once "vendor/autoload.php";
use BoldSign\Configuration;
use BoldSign\Api\DocumentApi;

$config = new Configuration();
$config->setApiKey('YOUR_API_KEY');

$documentApi = new DocumentApi($config);
$document_stream = $documentApi->downloadAuditLog($document_id = 'YOUR_DOCUMENT_ID', $on_behalf_of = 'ON_BEHALF_EMAIL');
```

```
ApiClient client = Configuration.getDefaultApiClient();
client.setApiKey("YOUR_API_KEY");
DocumentApi documentApi = new DocumentApi(client);
File documentStream = documentApi.downloadAuditLog("YOUR_DOCUMENT_ID", "ON_BEHALF_EMAIL");
```

```
import { DocumentApi } from "boldsign";

const documentApi = new DocumentApi();
documentApi.setApiKey("YOUR_API_KEY");

const documentStream = documentApi.downloadAuditLog("YOUR_DOCUMENT_ID", "ON_BEHALF_EMAIL");
```

## Real-world examples: How audit trails improve workflows

**Example 1: Vendor contracts**

A company automatically downloads the audit trail after every completed vendor contract and stores it alongside the signed PDF, reducing audit prep time and improving record consistency.

**Example 2: Legal disputes**

When a dispute arises, a legal team retrieves the audit trail to validate signing metadata such as signer identity, time stamps, IP address, and integrity checks, providing strong supporting evidence.

## Managing audit trails with BoldSign APIs

Audit trails are a foundational safeguard when your eSignature workflows need to prove authenticity, legal compliance, and transparency. With BoldSign APIs, you can:

- Download audit trails for documents you sent for signature.
- Retrieve audit trails for documents you sent for signature on behalf of others.
- Store audit trails alongside signed documents for audits, compliance reviews, or disputes.

## Conclusion

Audit trails are a simple but powerful way to strengthen document authenticity and operational transparency. With the [BoldSign API](https://boldsign.com/esignature-api.md), downloading audit trail PDFs is straightforward, so you can keep reliable signing evidence available for whenever you need it.

For more details, refer to the [BoldSign API documentation](https://developers.boldsign.com/documents/download-audit-trail).

Try [BoldSign for free](https://account.boldsign.com/signup?planId=1076\&utm_source=boldsignblogs\&utm_medium=redirect\&utm_campaign=boldsign) and If you need help setting this up in your workflow, reach out through the [support portal](https://support.boldsign.com/support/tickets/create) or schedule a [demo](https://boldsign.com/request-demo.md) with our team.

Topics [API integration](https://boldsign.com/blogs/tag/api-integration.md)[Security](https://boldsign.com/blogs/tag/security.md)

## Sign documents 3x faster

Send, sign and manage documents securely and efficiently.

[Try it today](https://account.boldsign.com/signup?planId=1018\&utm_source=boldsignblogs\&utm_medium=redirect\&utm_campaign=boldsign)

## Frequently asked questions

### What details does an audit trail include?

Audit trails typically capture signer identity, time stamps, IP addresses, and other signing activity details that help validate integrity and signing history. [View audit trail details.](https://developers.boldsign.com/how-to-guides/retrieve-esignature-document-history)

### Can I download on‑behalf audit trails?

Yes. Include the `onBehalfOf` parameter along with the `documentId`.

### Is an audit trail created for every signed document?

Yes. BoldSign generates an audit trail PDF when a document’s signature process is completed.

### Can I download audit trails for template and embedded signing workflows?

Yes. Audit trails are generated and downloadable for regular sends, template sends, embedded requests, and merged template workflows.

## Ranjitha Vazhivittan

Ranjitha is a skilled software developer with 3 years of experience at BoldSign. Alongside her technical expertise, she has a passion for writing and enjoys sharing thoughtful insights on technology and development. Beyond work, she stays curious by exploring emerging tools and trends, constantly seeking opportunities to learn and grow.

[More posts by Ranjitha Vazhivittan](https://boldsign.com/author/ranjitha-vazhivittan/)

## Related posts

- [Security](https://boldsign.com/category/security.md) June 17, 2025 3 min read

  ## [Staying Safe from Modern Phishing Attacks: A Guide for BoldSign Users](https://boldsign.com/blogs/boldsign-users-guide-for-phishing-attacks.md)

  Stay calm, BoldSign Users! Beat Modern Phishing Attacks with our expert guide on QR code scams, OAuth fraud & fake login page protection.

- [Security](https://boldsign.com/category/security.md) January 13, 2025 11 min read

  ## [Unveiling Security Flaws: Every Developer Needs to Know this!](https://boldsign.com/blogs/unveiling-security-flaws-every-developer-needs-to-know-this.md)

  Security flaws often hide in plain sight. This guide helps developers understand risks, avoid common mistakes, & build robust, secure applications from scratch.

- [API](https://boldsign.com/category/api.md) September 29, 2026 10 min read

  ## [How to Migrate from Docusign Without Losing Templates or Workflow Continuity](https://boldsign.com/blogs/migrate-from-docusign.md)

  Learn how to migrate from Docusign while protecting templates, signed records, and active workflows. Explore key risks, a practical checklist, and next steps.

Get started

## Sign up for your free trial today!

[Start free trial](https://account.boldsign.com/signup?planId=1018)

- 30-day free trial
- No credit card required

*Picture: A completed employment contract: signed by John Doe on 11/03/2026, all parties have signed*
