> 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/generate-via-template.md).

# Generate via template

- [Generate PDF in Android](https://docs.apryse.com/android/generate-via-template/generate-via-template.md): Here is your guide explaining how to generate document accurately and efficiently with Android using Apryse SDK
- [Document Generation Structured Input](https://docs.apryse.com/android/generate-via-template/generate-via-template/structured-input.md): Learn how to use a template engine to enhance your structured input with styled text, lists, hyperlinks, and headers in HTML or markdown. Contact us for feature suggestions! The Apryse Android SDK str
- [Document Generation Advanced Features in Android](https://docs.apryse.com/android/generate-via-template/generate-via-template/advanced.md): Discover advanced features for office templates, including custom tag delimiters and strict mode settings. Learn about explicit loop scope and table row insertion options. Optimize your template creat
- [Document Generation Data Model](https://docs.apryse.com/android/generate-via-template/data-model.md): Learn about using moustache templates and JSON dictionaries for structured content insertion in documents. Find out about error handling and various content value formats. Explore examples and image i
- [API for Document Generation via Template in Android](https://docs.apryse.com/android/generate-via-template/apis.md): Learn how to access Office template generation functionality with Android (Java/Kotlin) API functions. Explore com.pdftron.pdf.Convert#CreateOfficeTemplate and com.pdftron.pdf.TemplateDocument#fillTem


---

# 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/generate-via-template.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.