---
title: "Update the signed-in user's weekly/monthly report preferences (issue"
method: PATCH
path: "/api/v1/me/reports"
tags: ["Account"]
---

# Update the signed-in user's weekly/monthly report preferences (issue

`PATCH /api/v1/me/reports`

## Request

- Base URL: `https://api.uptimemonitoring.com`
- URL: `https://api.uptimemonitoring.com/api/v1/me/reports`
- Auth: HTTP bearer

Session-only, same 403 as `GET`. Body must be a JSON object with
at least one of `weekly`/`monthly`, each a plain JSON boolean —
not `null`, not a string or number. Any other top-level key is
rejected. Writes no audit event (a personal setting, not an
account mutation).

## Request body

- object
  - `weekly` boolean
  - `monthly` boolean

## Response `200`

Updated.

- ReportPreferences: A signed-in user's weekly/monthly uptime-report opt-ins on one account (issue #357) — stored per `account_members` row, not per user, so leaving one team's reports never silences another. `deliverable` is `true` exactly when `email` is non-null; a client can use it to prompt the user to verify an email address before expecting any report to actually arrive.
  - `account_id` integer
  - `weekly` boolean
  - `monthly` boolean
  - `email` string, nullable
  - `deliverable` boolean

## Other responses

- `400`: Invalid request.
- `403`: Not a dashboard session.

---

[API](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api.md) · [All operations](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/llms.txt) · [OpenAPI document](https://skmtc.dev/uptimemonitoring/apis/uptimemonitoring-com-api/revisions/ddcb2a8bc70f?raw)