Logo
Deploy Now

SaaS Alternative

OneSignal Pushover Twilio

Categories

Self-Hosted Open Source Automation DevOps API Notifications Alerting

Stars

1259

Forks

98

Watchers

9

Developer links

Last Updated: 07-24-2026 06:56 AM (UTC)

Apprise-API

One REST call, 130+ notification services: Apprise API wraps the well-known Apprise library in a lightweight Django/Gunicorn microservice, so "send an alert" works the same whether it goes to Slack, Discord, Telegram, Teams, email, SMS, Pushover, or PagerDuty - each addressed by a simple URL scheme. It solves the credential-sprawl problem cleanly: instead of embedding provider tokens in every app, cron job, and CI pipeline, you centralize them here and everything else just POSTs a body and title. Two modes cover every workflow. Stateless calls to /notify carry target URLs in the payload (or fall back to a default set via APPRISE_STATELESS_URLS); stateful mode stores named configurations server-side under keys, so /notify/{KEY} fans out to everything registered - with tag-based routing (comma for OR, space for AND) selecting which endpoints fire per message. Messages take info, success, warning, or failure types in text, Markdown, or HTML, with attachments up to a configurable size. A built-in web UI manages and tests configurations, APPRISE_CONFIG_LOCK makes the store read-only, service allow/deny lists restrict which schemes work, webhook remapping adapts third-party payloads, and a Prometheus /metrics endpoint watches the gateway itself.

Apprise-API

Benefits

  • Credentials Live in One Place
  • Apps POST plain messages - provider tokens stay centralized in the gateway.
  • 130+ Services, One Interface
  • Slack to SMS to email, all addressed by the same URL scheme.
  • Route by Tag, Not by Code
  • Comma-OR and space-AND tag logic selects endpoints per message.
  • Built for Production
  • Prometheus metrics, config locking, and service allow/deny lists.

Features

  • Stateless Notify
  • POST /notify with URLs in the payload or a default env-configured set.
  • Stateful Key Configs
  • Store configurations under keys; /notify/{KEY} fans out to all of them.
  • Message Types and Formats
  • Info, success, warning, failure - in text, Markdown, or HTML.
  • Attachments
  • File uploads with a configurable size cap (200 MB default).
  • Web Configuration UI
  • Manage and test notification configs in the browser, or disable for API-only.
  • Webhook Remapping
  • Adapt non-standard third-party payloads into notifications.