Apprise API

What is Apprise API?

Apprise API is a lightweight REST wrapper around the Apprise notification library that lets any app, script, or server send a message to 150+ services through one HTTP call. You configure your destinations once — Slack, Discord, Telegram, email, Pushover, and dozens more — and post to a single endpoint instead of integrating each provider’s SDK.

What is Apprise API best for?

Apprise API is best for developers and homelab operators who need one notification pipe across many tools without writing per-service integrations. It shines as a container sidecar or internal micro-service: cron jobs, CI pipelines, monitoring stacks, and self-hosted apps all curl the same endpoint, and you change where alerts go by editing config, not code.

What can Apprise API do?

• Deliver to 150+ notification services through one consistent API — Slack, Discord, Telegram, Matrix, email, SMS gateways, PagerDuty, Pushover, mobile push, and more.
• Run stateless (/notify/, destinations in the request) or stateful (/add/{KEY}, /notify/{KEY}) where named configs persist across restarts.
• Accept JSON, form-encoded, TEXT, or YAML payloads and configs, with tag-based grouping so one call can hit a subset of destinations.
• Attach local files or remote URLs to notifications (default 200MB limit, configurable).
• Serve a built-in web UI to create, store, and test notification configs without writing code.
• Expose /status health and Prometheus /metrics endpoints, and ship as a multi-arch Docker image (amd64, armv7, arm64).

Where does Apprise API fall short?

• No built-in authentication. By design it ships with no login or API-key layer, so anyone who can reach the endpoint can send through your stored configs. You must front it with a reverse proxy, network rules, or lock configs with APPRISE_CONFIG_LOCK — plan for that before exposing it.
• It’s a router, not a notification platform. It’s fire-and-forward: no delivery tracking, retry/queue guarantees, per-recipient subscription preferences, or templating engine. If you need audience management and analytics, a platform like Novu fits better.
• Stateful configs are flat files, not a database. Persisted configs are keyed by an ID on disk — fine for personal and infrastructure use, but there’s no multi-tenant user model or per-user subscription handling.

Is Apprise API free?

Yes — Apprise API is fully free and open source under the MIT license, with no paid tier, seat limits, or metered message counts. You self-host it (typically via the official Docker image), so your only costs are the server it runs on and whatever the downstream services charge (an SMS or push provider may bill separately).

What does Apprise API replace?

Apprise API stands in for parts of paid notification and messaging services like Twilio, OneSignal, and Pushover when your need is fan-out routing rather than a managed platform. It consolidates the “send this alert everywhere” job on your own infrastructure — though it relies on each destination service rather than delivering SMS or push itself, and it doesn’t replace those platforms’ delivery analytics or audience tools.

FAQ

Is Apprise API open source? Yes. It’s released under the permissive MIT license on GitHub (caronc/apprise-api), built on the equally open Apprise library, so you can self-host, modify, and redistribute it freely.

Can I self-host Apprise API for free? Yes. It’s designed to be self-hosted — the maintainer publishes a multi-architecture Docker image, and running it costs nothing beyond your own server. There’s no license fee or hosted paywall.

Is Apprise API a good Twilio or Pushover alternative? For fan-out routing, yes — it sends one message to 150+ services from a single endpoint at no per-message cost. But it’s a gateway, not a carrier: it delivers through services like SMS gateways or Pushover rather than replacing the underlying delivery network, and it has no built-in delivery analytics.

What do I need to run Apprise API? A host that can run the Docker container (or Python directly). It’s lightweight enough for a small VPS or Raspberry Pi. Because it has no built-in auth, put it behind a reverse proxy or restrict it to your private network. For a simpler single-topic push tool, compare ntfy.