> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/digital-signature.md).

# Digital signature

- [Server/Desktop Digital Signature Library](https://docs.apryse.com/core/digital-signature/signature.md): Sign, certify, and verify digital signatures in PDF documents with ease using our built-in certificate parsing feature. Learn how to add long-term validation and customize signature handling. Get star
- [Types of digital signatures supported in a PDF](https://docs.apryse.com/core/digital-signature/signature/sig-types.md): Learn about the different types of signatures supported in a PDF document, including certification, usage rights, and approval signatures. Discover how the Apryse SDK offers a high-level API for worki
- [Sign a PDF document on Server/Desktop](https://docs.apryse.com/core/digital-signature/sign-pdf.md): Learn how to digitally sign PDF files using the Apryse SDK. Add approval signatures with a Digital Certificate for authenticity and security. Full code sample provided. The Apryse Server SDK streamlin
- [Adding a certified signature field to a PDF on Server/Desktop](https://docs.apryse.com/core/digital-signature/certify-pdf.md): Learn how to add a certification signature field to a PDF document and digitally sign it with a full code sample using the digital signature API. Certify PDF/A documents for compliance effortlessly. T
- [Verify a signature on Server/Desktop](https://docs.apryse.com/core/digital-signature/verify-pdf.md): We offer a higher-level document-based API for verifying signatures, as well as a lower-level per-signature API. Page includes code samples.
- [Add a DocTimeStamp signature on Server/Desktop](https://docs.apryse.com/core/digital-signature/dts.md): Set doctimestamp in PDF on Server/Desktop to add authenticity to the document.  Learn how to add trusted certifictae using WebViewer.
- [Add Long-Term Validation (LTV) information for a signature on Server/Desktop](https://docs.apryse.com/core/digital-signature/ltv.md): Learn how to enable LTV to digital signature in PDF either signed internally or externally.  The Apryse Server SDK streamlines secure document processing with robust support for C#, C++, Java, JavaScr
- [Custom Signing on Server/Desktop](https://docs.apryse.com/core/digital-signature/custom-signing.md): Discover how to customize your document signing process with the Apryse custom signing API. Integrate PDF-specific operations, HSM tokens, cloud keystores, and more for a seamless signing experience.
- [Embedded Timestamp Tokens with custom signing API on Server/Desktop](https://docs.apryse.com/core/digital-signature/emb-tst.md): Learn how to create and insert secure timestamp tokens with the custom signing API for PAdES-format signature conformance. Ensure verifiability by adding trusted root certificates. Enable online CRL r
- [Code samples for adding digital signatures to PDFs on Server/Desktop](https://docs.apryse.com/core/digital-signature/samples.md): Digitally sign PDF files with ease using this high-level API. Learn how to sign and certify documents efficiently. Perfect for secure document management. The Apryse Server SDK streamlines secure docu
- [API for digital signatures on Server/Desktop](https://docs.apryse.com/core/digital-signature/apis.md): Learn about classes for handling digital signatures in PDF documents with C++, Java, Android, Web, Node.js, .NET, .NET Core, iOS, Xamarin, and UWP. Explore pdftron::SDF::SignatureHandler, com.pdftron.


---

# 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://docs.apryse.com/core/digital-signature.md?ask=<question>&goal=<user_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.
