> 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/portfolios.md). # Portfolios - [Create PDF portfolio or package in Android](https://docs.apryse.com/android/portfolios/portfolio.md): Create a dynamic PDF portfolio with the ability to integrate various file types. Learn how to create a PDF portfolio containing multiple file types and get started today! The Apryse Android SDK stream - [Create a PDF portfolio (package) in Android](https://docs.apryse.com/android/portfolios/create.md): Learn how to create a PDF portfolio with multiple file types using our full code sample. Explore how to create, extract, and manipulate PDF Packages efficiently. The Apryse Android SDK streamlines sec - [Sample to create PDF packages in Android](https://docs.apryse.com/android/portfolios/samples.md): Learn how to create, extract, and manipulate PDF packages (portfolios) with this sample. Enhance your PDF skills and efficiency today! The Apryse Android SDK streamlines secure document processing and - [APIs for creating PDF packages in Android](https://docs.apryse.com/android/portfolios/apis.md): Discover utility classes for portfolios with PDF documents in Android using com.pdftron.pdf.PDFDoc. Enhance your app development with these Java/Kotlin tools. The Apryse Android SDK streamlines secure --- # 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/portfolios.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.