> 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/events.md). # Events - [Work with WebViewer Loading Events](https://docs.apryse.com/web/events/loading-events.md): Learn about the order of events when WebViewer is instantiated and a document is loaded. Understand the key steps and interactions for optimal usage. The Apryse Web SDK streamlines secure, serverless - [Interact with Viewer Events](https://docs.apryse.com/web/events/viewer-events.md): Enhance user experience with WebViewer by leveraging various events triggered in response to interactions. Learn how to optimize behavior and update annotations as users navigate through pages. The Ap - [Listening to WebViewer UI events](https://docs.apryse.com/web/events/ui-events.md): Explore the UI namespace in WebViewer for APIs and objects related to the default UI. Learn how to trigger events and customize interactions with the UI elements effectively. The Apryse Web SDK stream - [Interact with Annotation Events in WebViewer JavaScript PDF Viewer](https://docs.apryse.com/web/events/events.md): Discover key Annotation Events for efficient integration. Learn to track creation, modification, deletion, and selection of annotations using AnnotationManager using web. Optimize workflows with preci - [Getting text from text select events](https://docs.apryse.com/web/events/text-select-events.md): Learn how to extract selected text from a loaded document to create annotations or free text annotations. Explore more on text extractions in our guides! The Apryse Web SDK streamlines secure, serverl --- # 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/web/events.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.