`bullpen notifications mark-multiple`¶

Last updated: July 13, 2026

Mark multiple notifications as read

Usage¶

bullpen notifications mark-multiple [OPTIONS] <ID>...

Live Help¶

Mark multiple notifications as read

Usage: bullpen notifications mark-multiple [OPTIONS] <ID>...

Arguments:
  <ID>...
          Notification IDs to mark as read

Options:
      --output <OUTPUT>
          Output format for command results

          [possible values: table, json]

      --env <ENV>
          Target environment to connect to (overrides config.toml)

          [env: BULLPEN_ENV=]
          [possible values: staging, production]

      --config <CONFIG>
          Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).

          Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.

      --read-only
          Enable read-only mode: blocks all mutating commands

      --non-interactive
          Suppress interactive prompts; does NOT imply --yes for money-moving commands

          [env: BULLPEN_NON_INTERACTIVE=]

  -h, --help
          Print help (see a summary with '-h')

EXAMPLES:
  # Review notifications before marking several as read
  bullpen notifications list

  # Mark several notifications as read; this changes notification state
  bullpen notifications mark-multiple notif-1,notif-2

  # Export the multi-mark result as JSON
  bullpen notifications mark-multiple notif-1,notif-2 --output json

Example Commands¶

bullpen notifications mark-multiple --help

JSON Output¶

Contract: JSON Output Contract.

Successful output is a single JSON document. The shape below is representative for this command family; commands may add fields without breaking the shared contract.

Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.

Top-level Keys¶

key	type	nullable	notes
`status`	string	no	`marked` after the requested notifications are marked read
`ids`	array	no	Notification IDs requested by the command
`requested_count`	integer	no	Number of IDs sent to the server

Example¶

bullpen notifications mark-multiple notif-1,notif-2 --output json

{
  "status": "marked",
  "ids": [
    "notif-1",
    "notif-2"
  ],
  "requested_count": 2
}

Stability¶

Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.

bullpen notifications mark-multiple¶