Skip to main content

PagerDuty On-Call Ack

pagerduty-oncall-ack installs the pd-auto-ack CLI. It acknowledges PagerDuty incidents only when the configured user is currently on call.

It is intentionally narrow:

  • Checks whether the user is on call.
  • Displays open incidents assigned to that user.
  • Acknowledges only triggered incidents.
  • Does not resolve, reassign, rename, or add notes to incidents.

Install

Recommended install uses pipx, which keeps CLI tools in isolated Python environments.

macOS with Homebrew:

brew install pipx
pipx ensurepath
exec zsh -l

Linux:

python3 -m pip install --user pipx
python3 -m pipx ensurepath
exec "$SHELL" -l

Install the CLI:

pipx install pagerduty-oncall-ack
pd-auto-ack --version

Upgrade an existing install:

pipx upgrade pagerduty-oncall-ack

If you installed an older release when the package was named pagerduty-auto-ack, reinstall once under the new package name:

pipx uninstall pagerduty-auto-ack
pipx install pagerduty-oncall-ack

The CLI command remains pd-auto-ack.

Quick Start

Create a starter config file:

pd-auto-ack init --env-file ~/.pd-auto-ack.env
nano ~/.pd-auto-ack.env

Validate configuration and PagerDuty access:

pd-auto-ack doctor --env-file ~/.pd-auto-ack.env
pd-auto-ack check --env-file ~/.pd-auto-ack.env

Run one dry-run cycle:

pd-auto-ack run --env-file ~/.pd-auto-ack.env --once

Run continuously in dry-run mode:

pd-auto-ack run --env-file ~/.pd-auto-ack.env --watch --interval 30

Run continuously in live mode:

pd-auto-ack run --env-file ~/.pd-auto-ack.env --watch --interval 30 --apply

Required PagerDuty Access

The PagerDuty token needs permissions equivalent to:

  • oncalls.read
  • incidents.read
  • incidents.write

Documentation

Security

Please report suspected vulnerabilities through GitHub's private vulnerability reporting flow from the repository Security tab. See SECURITY.md.

Safety Summary

The CLI only acknowledges incidents when all of these are true:

  • the configured user is currently on call
  • the incident is triggered
  • the incident is assigned to that user

Dry-run mode is the default. Live mode requires --apply or PD_APPLY=true.

API References

The implementation follows PagerDuty's REST API reference and published OpenAPI schema:

Metadata

Release files for pagerduty-oncall-ack 0.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pagerduty-oncall-ack 0.4.1
File Size Uploaded
pagerduty_oncall_ack-0.4.1.tar.gz 13.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pagerduty-oncall-ack 0.4.1
File Interpreter ABI Platform
pagerduty_oncall_ack-0.4.1-py3-none-any.whl Python 3 none any Details

Total release size: 26.2 kB

Release files / pagerduty_oncall_ack-0.4.1.tar.gz

Download URL pagerduty_oncall_ack-0.4.1.tar.gz
Size 13.7 kB
Tags Source
SHA-256 checksum
How to use checksums
50240933fa87d7d12399e86e2a0a1e5aab3ffc07c51bfcb13610402abfd5b469
BLAKE2b-256 checksum
How to use checksums
6c83922d22ba7a72a37558d0eff3a8c40e0b5e09107ae6dc86d4595b94866871
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Release files / pagerduty_oncall_ack-0.4.1-py3-none-any.whl

Download URL pagerduty_oncall_ack-0.4.1-py3-none-any.whl
Size 12.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
dc0dc1d4b09116dc01395f7ec0727090a4ba2f25fb3ec716ea0acf117af41887
BLAKE2b-256 checksum
How to use checksums
e6cd355b1378ed338d3e7e0fb0f1b4dd7510ee5beec783e9fb1a3294f48b33d4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.

Transparency log

Release history Release notifications | RSS feed

0.6.0

2 release files

0.5.0

2 release files

This release

0.4.1 This release

2 release files

0.4.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page