> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/use/source-code/form-service.md).

# Form service

**Sunbird-ED Forms API** is primarily used for **configuring and managing forms** within the Sunbird-ED platform. These forms are likely used for various purposes, such as:

* **User registration**
* **Content creation**
* **Feedback collection**
* **Other administrative tasks**

**Key functionalities of the API might include:**

* Creating, updating, and deleting form definitions.
* Managing form fields (text boxes, dropdowns, etc.) and their properties.
* Defining form layouts and structures.
* Handling form submissions and data processing.
* Integrating forms with other Sunbird-ED components.

#### How it Enables Dynamic Configuration

While the specific details of the API might vary, it's reasonable to assume that the Sunbird-ED Forms API provides mechanisms for:

* **Defining form templates:** Creating reusable form structures.
* **Customising form instances:** Populating form templates with specific data and configurations.
* **Managing form submissions and data:** Processing and storing form data.

By allowing for dynamic configuration of forms, the API can be used to create flexible and adaptable user interfaces within the Sunbird-ED platform.


---

# 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://ed.sunbird.org/use/source-code/form-service.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.