WardenPoint Python SDK
Official Python SDK for WardenPoint — incident alerting and on-call escalation. Fire and manage alerts from your apps, jobs and pipelines; page on-call automatically when code fails.
Install
pip install wardenpoint
Quickstart
from wardenpoint import WardenPoint
wp = WardenPoint(api_key="wp_live_xxx") # or set WARDENPOINT_API_KEY
# send to a recipient (UUID or exact name) at a priority
wp.alerts.send(recipient="ops-oncall", message="DB primary down", priority="high")
# send to a whole group
wp.alerts.send_to_group(group="<group-uuid>", message="API SLO burn", priority="critical")
# fire a pre-configured template
wp.templates.fire("disk-full", vars={"host": "web-3", "pct": 95}, override={"priority": "high"})
# inspect / acknowledge / cancel
wp.alerts.list()
wp.alerts.status("<id>")
wp.alerts.acknowledge("<uuid>")
wp.alerts.cancel("<uuid>")
wp.recipients.list()
Priorities: low, normal, high, critical.
templates.fire(...) requires alert templates to be enabled for your company
(a per-tenant setting in the dashboard); otherwise the call returns an
APIError.
Page automatically when code fails
The context manager and decorator alert on-call with the exception and traceback if the wrapped code raises — then re-raise, so behaviour is unchanged otherwise. A delivery failure never masks your original error.
# context manager
with wp.guard(group="sre", title="nightly ETL"):
run_etl()
# decorator for jobs
@wp.on_failure(to="ops-oncall", priority="high")
def reconcile_invoices():
...
Configuration
| Setting | Argument | Environment |
|---|---|---|
| API key | api_key= |
WARDENPOINT_API_KEY |
| Base URL | base_url= |
WARDENPOINT_BASE_URL (default https://wardenpoint.com/api/v1) |
| TLS verify | verify= |
— (set False only for self-hosted/staging with self-signed certs) |
WardenPoint is also a context manager (closes the HTTP client on exit):
with WardenPoint(api_key="...") as wp:
wp.alerts.send(recipient="...", message="...")
Errors
wardenpoint.APIError— non-2xx response (.status,.message,.body).wardenpoint.WardenPointError— config / validation / resolution errors.
Development
python -m venv .venv && . .venv/bin/activate
pip install -e ".[dev]"
pytest
License
MIT — see LICENSE.
Metadata
Release files for wardenpoint 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| wardenpoint-0.1.0.tar.gz | 8.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wardenpoint-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.5 kB
Release files / wardenpoint-0.1.0.tar.gz
| Download URL | wardenpoint-0.1.0.tar.gz |
|---|---|
| Size | 8.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ff772264c5fd59a05d2adf921ef9d16686bbe1ec03a466c3f13c2348ad9dd95
|
|
BLAKE2b-256 checksum How to use checksums |
585257da9c5f14d060235696e30e8466e5467922c2aeab52fff9099b46eeb3d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 14, 2026.
Transparency logRelease files / wardenpoint-0.1.0-py3-none-any.whl
| Download URL | wardenpoint-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0a654126fa5abe0c07cf0c0b94cfe83aea3ad792e41ed61ab40f12d82b5dd73
|
|
BLAKE2b-256 checksum How to use checksums |
aae258dad4a9d8e4aedaf82c784353ff64bd08652220fdd861e25c0082b94bbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 14, 2026.
Transparency log