Skip to main content

About Secured Signal API

Secured Signal API is a secure, configurable proxy for Signal CLI REST API.
It does not replace or modify the original API — it sits in front of it, adding a layer of control, authentication, and flexibility for production use.

What It Is​

The Signal CLI REST API provides a robust HTTP interface to the Signal Messenger service.
Secured Signal API works as a reverse proxy, forwarding approved requests to your existing Signal CLI REST API instance, while managing access and configuration.

It's designed for developers who want to:

  • Restrict or log certain API calls,
  • Enforce authentication,
  • Add templating or request preprocessing,
  • And deploy everything neatly via Docker.

Key Features​

  • 🔒 Access Control — Protect your Signal API with token-based authentication and endpoint restrictions.
  • 🧩 Full Compatibility — 100% protocol-compatible; all requests are still handled by your existing Signal CLI REST API.
  • ⚙️ Configurable Proxy Behavior — Define templates and limits via YAML or environment variables.
  • 🧠 Message Templates — Use variables and placeholders to standardize common message formats.
  • 🐳 Docker-Ready — Comes packaged for containerized environments, deployable in seconds.
  • and much more...

Architecture Overview​

Secured Signal API acts purely as a gateway — it never bypasses or replaces your existing Signal CLI REST API: