> 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/web/get-started/readme/outsystems.md).

# How to integrate WebViewer into a Outsystems PDF Viewer

Integrate Outsystems pdf viewer for viewing, annotating, editing, and creating PDFs in Mendix. Process documents natively in Mendix without third-party applications.

This guide will help you **integrate a free trial of WebViewer into an OutSystems Reactive Web App**.

The easiest way to get started would be to download the WebViewer Forge component available here:

{% @apryse-download-button/apryse-download-button id="WebViewer\_Forge\_Component\_web\_web" title="WebViewer Forge Component" showVersion="false" %}

Get your Apryse trial key.

{% @apryse-license-key/apryse-license-key platform="WEB\_VIEWER" variant="full" %}

From here, you will have a working skeleton of how to integrate Apryse into an OutSystems Reactive Web App.

More detailed instructions are coming soon, but if you have any questions about this integration, please feel free to contact us at the [Trial Support Form](https://apryse.com/form/trial-support) and we'd be happy to provide further guidance.

Should you need OutSystems support, the OutSystems team can be reached at [`developers@outsystems.com`](mailto:developers@outsystems.com).


---

# 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 dynamically 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/web/get-started/readme/outsystems.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 `build a script that syncs our docs to a CMS` 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.