---
title: "Update a recall"
method: PUT
path: "/recalls/{recallId}"
tags: ["recalls"]
---

# Update a recall

`PUT /recalls/{recallId}`

## Path parameters

- `recallId` string, required

## Response `200`

Recall updated

- RecallResponse — Represents a patient recall, a record used to bring a patient back in for a follow-up visit or overdue care based on a scheduled trigger date. It tracks status through the recall lifecycle (pending, active, scheduled, inactive) and links to the source (upload, UI, or EHR integrator).
  - `_id` string, required — Luma's internal ID of an object.
  - `user` string — The ID of the root account user.
  - `deleted` 0 | 1 — Flag for logical deletion where 1 means deleted.
  - `createdBy` string — The ID of the user who created this object.
  - `updatedBy` string — The ID of the user who updated this object.
  - `createdAt` string, date-time — The date/time when this object was created.
  - `updatedAt` string, date-time — The date/time when this object was updated.
  - `patient` string — patient
  - `provider` string — provider
  - `facility` string — facility
  - `appointment` string — appointment
  - `type` string — appointmentType
  - `date` string — date
  - `source` 'upload' | 'ui' | 'integrator' — source
  - `status` 'active' | 'pending' | 'scheduled' — status
  - `attempt` string — attempt

## Other responses

- `401` — Not authenticated
- `403` — Access token does not have the required scope

---

[API](https://skmtc.net/lumahealth/apis/rest-service.md) · [All operations](https://skmtc.net/lumahealth/apis/rest-service/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lumahealth/rest-service/revisions/d3c75c2a2f1d/schema)