# Feedback

Endpoints for working with feedback.

## Computes feedback for an existing task.

 - [POST /tasks/${taskId}/feedback/compute](https://developers.taskbase.com/apis/specification/feedback/computefeedbackbytaskid.md): This endpoint works for tasks that have already been registered.


## Computes feedback for the provided task and answer

 - [POST /feedback/compute](https://developers.taskbase.com/apis/specification/feedback/computefeedback.md): This operation provides access to our formative feedback. The task included in the request is essential for context and must be provided with every request. This ensures synchronization and prevents issues where feedback might be based on an outdated version of the task.


The  field in the task object is crucial for identifying answers associated with the same task. This field represents the task's identifier as defined in the client’s system.

If the id remains the same across requests but other task fields change, the system updates the fields for the existing task 𝑡. Feedback is then generated based on previously submitted answers and feedback related to task 𝑡 (). If the system has not seen the value of the  field before, a new task 𝑡′ is created. In this case, there are no existing answers or feedback linked to task 𝑡′.

To avoid unintended behavior, only change the id field when creating a completely new task.


() This applies only if the task types remain the same. If a request specifies a task type for t that differs from the type already associated with it from previous requests, an error will be returned.
---

: Whenever a task is updated in the client's system, it should be assumed that these changes affect the feedback. Therefore, we recommend the following actions to align with the changes: test the feedback after making changes; create new answers to reflect the updated task; and consider reassigning existing feedback for previous answers. Without these measures, the generated feedback may no longer be accurate.