> 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/android/digital-signature/samples.md).

# Code samples for adding digital signatures to PDFs in Android

Learn how to digitally sign PDF files with this high-level API demo. Check out UI samples and an Android showcase app for more features. Try the digital signature demo now! The Apryse Android SDK stre

[Digitally sign PDF files](/android/get-started/samples.md#digitalsignatures) Demonstrates the basic usage of the high-level API for digital signature-related operations such as signing and certification.

## UI samples

{% hint style="info" %}
Please note that **native code** is being used in the following showcase app(s). Apryse SDK for Xamarin provides the same features but the source code for the showcase application(s) is only available in native languages.
{% endhint %}

[Android showcase sample app](/android/samples/package-samples/sample-showcase.md) The showcase demonstrates some features of the SDK. To view the signature demo, select `Digital Signature` found under `PDF Form` in the app.


---

# 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/android/digital-signature/samples.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.