---
title: "Dismiss a meeting reminder on every device of the user"
method: POST
path: "/notifications/calendar-events/dismiss"
tags: ["notifications"]
---

# Dismiss a meeting reminder on every device of the user

`POST /notifications/calendar-events/dismiss`

## Request

- Base URL: `https://api.focusbear.io` (the document declares no server; this is the origin it was published from)
- URL: `https://api.focusbear.io/notifications/calendar-events/dismiss`
- Auth: HTTP bearer

Call this when the user joins or silences a meeting on one device, so the rest stop alerting. The meeting is identified by `summary` and `event_begins` rather than by a calendar id, because the Mac app, the phone and the backend each know the same meeting by a different id. Events that the backend has never synced are accepted too: the other devices still hold their own copy. The dismissal is broadcast both as a silent FCM/Beams push (mobile) and as a `late-no-more-event-dismissed` Pusher Channels event on `private-<userId>` (desktop); send `device_id` to have your own device echoed back so you can ignore your own event.

## Request body

- DismissCalendarEventDto
  - `summary` string, required
  - `dismiss_reason` string
  - `event_begins` string, date-time, required
  - `device_id` string, uuid: The device reporting the dismissal. Echoed back in the broadcast so the sender can ignore its own event — the same convention every other `private-<userId>` trigger follows (`settings-updated`, `blocking-schedule-updated`). Optional: a client that does not send it simply has to tolerate its own echo.

## Response `204`

---

[API](https://skmtc.dev/focusbear/apis/focusbear-api.md) - [All operations](https://skmtc.dev/focusbear/apis/focusbear-api/llms.txt) - [OpenAPI document](https://skmtc.dev/focusbear/apis/focusbear-api/revisions/3a83a3b9a811?raw)
