> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/sign/en/advanced-features/sign-and-flows/download-audit-trail.md). # Download the audit trail Retrieve the audit trail from Salesforce ## Action name: "Download Audit Trail" The audit trail is a detailed document that contains all the important information about the signature. It serves as a guarantee in case of dispute, making it possible to technically trace the electronic signature procedure. This flow action lets you retrieve the audit trail once the signature procedure is complete. The expected parameter is: * **Delivery, Recipient or ContentVersion Id**: the ID of the Delivery, Recipient or ContentVersion for which you want to retrieve the audit trail * **ContentVersion Id**: enter a ContentVersion Id to get the audit trail of an electronic seal. The audit trail is only retrieved if an electronic seal has already been applied to the document By providing a Recipient ID, the audit trail is retrieved as a PDF and stored directly in the Recipient's files. By providing a Delivery ID, the audit trail is retrieved as a PDF and stored directly in the Delivery's files. If there are multiple recipients, the audit trails are merged into a single PDF on the Delivery --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://university.gonexa.fr/sign/en/advanced-features/sign-and-flows/download-audit-trail.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.