---
title: "Updates Task Resource"
method: PUT
path: "/fhir/v2/Task/{id}"
tags: ["Tasks/Recalls"]
---

# Updates Task Resource

`PUT /fhir/v2/Task/{id}`

## Request

- Base URL: `https://stage.ema-api.com/ema-dev/firm/apiportal/ema`
- URL: `https://stage.ema-api.com/ema-dev/firm/apiportal/ema/fhir/v2/Task/{id}`
- Auth: HTTP bearer and API key in header `x-api-key`

Updates an existing EMA Task. `Task.id` must be a valid `TASK|<integer>` identifier for an existing task — PM Recall ids are rejected. At least one assignee in `input` is required, same as create (see the create operation for the assignee shape). **The following fields are immutable after creation and will be rejected if changed from their current stored value:** `authoredOn`, `description`, `location`, `for` (patient), and `status`. Only priority, assignees (`input`), notes, and the optional reference fields can effectively be changed on update.

## Path parameters

- `id` string, required

## Request body

- FHIRJSONRESOURCE: A FHIR resource

## Response `200`

Success

- FHIRJSONRESOURCE: A FHIR resource

## Other responses

- `400`: BAD REQUEST - The request was bad, often due to a missing required parameter
- `401`: NOT AUTHORIZED - Authentication error; this token is not allowed access to the API
- `403`: FORBIDDEN
- `404`: NOT FOUND
- `422`: UNPROCESSABLE ENTITY - Request could not be processed; typically a validation error
- `429`: TOO MANY REQUESTS - Request was rate limited (1000 calls/min default); please retry
- `500`: SERVER ERROR - Internal Server Error

---

[API](https://skmtc.dev/modmed/apis/ema-proprietary-api.md) - [All operations](https://skmtc.dev/modmed/apis/ema-proprietary-api/llms.txt) - [OpenAPI document](https://skmtc.dev/modmed/apis/ema-proprietary-api/revisions/c03c1956a05d?raw)