> 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/forms/apis.md).

# APIs for PDF form filling

Discover a comprehensive guide on Annotations, Field Management, and Form Field Creation with PDFNet's API. Learn about AnnotationManager, FieldManager, FormFieldCreationManager, and more. The Apryse

[Annotations](https://sdk.apryse.com/api/web/Core.Annotations.html) A namespace containing annotation classes.

[AnnotationManager](https://sdk.apryse.com/api/web/Core.AnnotationManager.html) A control class used for managing annotations.

[Field](https://sdk.apryse.com/api/web/Core.Annotations.Forms.Field.html) A class defining a PDF field.

[FieldManager](https://sdk.apryse.com/api/web/Core.Annotations.Forms.FieldManager.html) A control class used for managing fields.

[FormFieldCreationManager](https://sdk.apryse.com/api/web/Core.FormFieldCreationManager.html) A control class used for form field creation and editing.

[WidgetAnnotation](https://sdk.apryse.com/api/web/Core.Annotations.WidgetAnnotation.html) A class defining widget annotations that are associated with fields.

## Full API

{% hint style="info" %}
[Full API](/web/what-is-webviewer/full-api.md) is mainly used for PDF processing situations that are not featured using the Standard API. The preferred recommendation is to use the Standard API to address your situation when possible. Standard API is easy to use, loaded by default, and performs best for most situations.
{% endhint %}

[PDFNet.FDFDoc](https://sdk.apryse.com/api/web/Core.PDFNet.FDFDoc.html) A class representing FDF documents.

[PDFNet.FDFField](https://sdk.apryse.com/api/web/Core.PDFNet.FDFField.html) A class representing interactive form fields.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/web/forms/apis.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.