> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/apis/using-the-task-form-values-api-call.md). # Using the Task Form Values API call Submit and update form values for active tasks via the API. Task must be assigned and form submitted; completed or delayed tasks prevent modifications **Question: How can the Task Form Values API be used, and under what conditions can form data be modified?** Answer: The Task Form Values API is used to submit and update form data associated with a task in the platform. A key requirement is that the task must first be assigned to a user, and the form must be submitted before any modifications can be attempted. If the form has not been submitted, the API returns a response indicating the problem. A crucial factor is the task status. Once a task is marked as completed, failed, or delayed, no further modifications can be made, as this restriction preserves the integrity of the submitted data. However, if the task remains in an active state—such as unassigned, assigned, or arrived—the API can still be used to update form values, even after the initial submission. Each successful update triggers a notification in the application indicating that the form has been submitted. In short, the API works effectively for updates only when the task is active and the form has already been submitted. Otherwise, modifications aren't allowed. **Links:** [Form/Value/Update API call](/docs/navixy-api/user-api/resources/field-service/task/form/values.md#post-task-form-values-update) --- # 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://navixy.com/docs/qna/apis/using-the-task-form-values-api-call.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.