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: .github/templates/README.template.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,14 +24,19 @@ Take a look at traefik implementation:
24
24
25
25
Before you can send messages via `secured-signal-api` you must first setup [`signal-api`](https://github.com/bbernhard/signal-cli-rest-api/blob/master/doc/EXAMPLES.md),
26
26
27
-
to send messages you have to either:
27
+
to be able to use the API you have to either:
28
28
29
29
-**register a Signal Account**
30
30
31
31
OR
32
32
33
33
-**link Signal API to an already registered Signal Device**
34
34
35
+
> [!Hint]
36
+
> It is advised to do this by directly accessing `signal-api`
37
+
> As Secured Signal API blocks the `/register` and `/qrcodelink` by default.
38
+
> If you really want to you can do this with Secured Signal API by removing these endpoints from the Blocklist
39
+
35
40
## Usage
36
41
37
42
Secured Signal API implements 3 Ways to Authenticate
0 commit comments