> 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/what-is-webviewer/full-api.md).

# Full API for PDF processing

Discover the full API for complete client-side PDF processing solutions. Learn about advanced features and operations available with this powerful tool. Optimize your PDF processing now! The Apryse We

The full API is a complete client-side browser solution to PDF processing.

It is mainly used for PDF processing situations that are not featured using the [standard API](/web/what-is-webviewer/usage.md). The preferred recommendation is to use the [standard API](/web/what-is-webviewer/usage.md) to address your situation when possible. The [standard API](/web/what-is-webviewer/usage.md) is easy to use, loaded by default, and performs best for most situations.

## Get started

[Setup WebViewer for full API](/web/full-api/setup.md) To setup WebViewer to process PDF documents using the full API.

[Running full API without the viewer](/web/full-api/running-without-viewer.md) To setup full API PDF processing to run without the viewer.

[Advanced features](/web/full-api/advanced-features.md) An introduction to advanced features with the full API.

[More operations](/web/full-api/operations.md) To access more operations available with the full API.


---

# 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/what-is-webviewer/full-api.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.