---
title: "Remove a flow override"
method: DELETE
path: "/v1/notifications/preferences/flows/{flowId}"
tags: ["notifications"]
---

# Remove a flow override

`DELETE /v1/notifications/preferences/flows/{flowId}`

## Request

- Base URL: `https://api.flowral.app`
- URL: `https://api.flowral.app/v1/notifications/preferences/flows/{flowId}`
- Auth: one of:
  - HTTP bearer
  - OAuth 2 (client credentials, token URL `https://api.flowral.app/v1/oauth/token`, scopes: `notifications:write`)

The flow follows the person's account settings again. Not the same as turning everything off for it.

## Path parameters

- `flowId` string, required

## Query parameters

- `memberId` string, required: The person these settings belong to. A credential has no inbox, so this is never optional.

## Response `200`

SUCCESS

- NotificationPreferences: What one person is emailed about, resolved. When `flowId` is set, this is the account settings with that flow's override already applied.
  - `memberId` string, required
  - `flowId` string, nullable: Null for the account-level answer.
  - `email` boolean, required: The master switch. False means no notification email at all, whatever the per-event flags say.
  - `muted` boolean: Set by a flow-level override to silence one flow.
  - `events` object, required: Per-event switches.
    - `assigned` boolean: A task was assigned to them.
    - `unlocked` boolean: A task of theirs stopped being blocked.
    - `digest` boolean: The morning summary. Account level only.
  - `timezone` string: IANA zone. The digest is sent in this person's morning.
  - `digestHour` integer: 0–23, local.

## Other responses

- `401`: UNAUTHORIZED
- `403`: FORBIDDEN · INSUFFICIENT_SCOPE
- `404`: NOT_FOUND · MEMBER_NOT_FOUND
- `429`: RATE_LIMITED

---

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