> 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/xamarin/pdf-a.md). # PDF/A - [PDF/A Conversion Library in Xamarin](https://docs.apryse.com/xamarin/pdf-a/pdfa.md): Convert generic PDF documents to PDF/A with our API. Validate existing PDF/A files easily. Learn how to pick the right version of PDF/A for archiving. Explore our tools & utilities for PDF/A managemen - [Convert PDF to PDF/A in Xamarin](https://docs.apryse.com/xamarin/pdf-a/convert.md): Convert PDF to PDF/A format with ease using our comprehensive tool. Validate and convert PDF documents to PDF/A compliance effortlessly. Get detailed reports on changes made during the conversion proc - [Validate PDF/A documents in Xamarin](https://docs.apryse.com/xamarin/pdf-a/validate.md): Validate all versions of PDF/A in Xamarin. All you need is full API enabled in WebViewer to validare pdf/a in Xamarin. - [Code samples to validate & convert PDF to PDF/A in Xamarin](https://docs.apryse.com/xamarin/pdf-a/samples.md): Convert PDF to PDF/A with this sample illustrating how to validate existing PDF documents for PDF/A compliance and convert generic PDFs to PDF/A format. The Apryse Xamarin SDK streamlines secure, serv - [APIs for PDF/A conversions & validation in Xamarin](https://docs.apryse.com/xamarin/pdf-a/apis.md): Learn about utility classes for PDF/A or PDF documents in Xamarin.Android and Xamarin.iOS using C# with pdftron.PDF.PDFA.PDFACompliance. Optimize your PDF files now! The Apryse Xamarin SDK streamlines --- # 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/xamarin/pdf-a.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.