You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/about.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ It does **not** replace or modify the original API — it sits in front of it, a
10
10
11
11
---
12
12
13
-
## 💡 What It Is
13
+
## What It Is
14
14
15
15
The [Signal CLI REST API](https://github.com/bbernhard/signal-cli-rest-api) provides a robust HTTP interface to the Signal Messenger service.
16
16
**Secured Signal API** works as a **reverse proxy**, forwarding approved requests to your existing Signal CLI REST API instance, while managing access and configuration.
@@ -24,7 +24,7 @@ It’s designed for developers who want to:
24
24
25
25
---
26
26
27
-
## 🔧 Key Features
27
+
## Key Features
28
28
29
29
- 🔒 **Access Control** — Protect your Signal API with [**token-based authentication**](./configuration/api-tokens) and [**endpoint restrictions**](./features).
30
30
- 🧩 **Full Compatibility** — 100% protocol-compatible; all requests are still handled by your existing Signal CLI REST API.
@@ -34,7 +34,7 @@ It’s designed for developers who want to:
34
34
35
35
---
36
36
37
-
## 🏗 Architecture Overview
37
+
## Architecture Overview
38
38
39
39
Secured Signal API acts purely as a **gateway** — it never bypasses or replaces your existing **Signal CLI REST API**:
0 commit comments