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: README.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -197,9 +197,9 @@ Supported types include **strings**, **ints** and **arrays**
197
197
In order to differentiate Injection Queries and _regular_ Queries
198
198
you have to add `@` in front of any KeyValue Pair assignment.
199
199
200
-
### Environment Variables
200
+
## Environment Variables
201
201
202
-
#### API Token(s)
202
+
### API Token(s)
203
203
204
204
Both `API_TOKEN` and `API_TOKENS` support multiple Tokens seperated by a `,` **Comma**.
205
205
During Authentication Secured Signal API will try to match the given Token against the list of Tokens inside of these Variables.
@@ -221,7 +221,7 @@ like Blocked Endpoints and any sort of Auth.
221
221
> [!NOTE]
222
222
> Blocked Endpoints can be reactivated by manually setting them in the Environment
223
223
224
-
####Blocked Endpoints
224
+
### Blocked Endpoints
225
225
226
226
Because Secured Signal API is just a Proxy you can use all of the [Signal REST API](https://github.com/bbernhard/signal-cli-rest-api/blob/master/doc/EXAMPLES.md) endpoints except for...
227
227
@@ -250,7 +250,7 @@ By default Secured Signal API provides the following Placeholders:
250
250
- **NUMBER** = _ENV_: `NUMBER`
251
251
- **RECIPIENTS** = _ENV_: `RECIPIENTS`
252
252
253
-
#### Customization
253
+
### Customization
254
254
255
255
Placeholders can be added by setting `VARIABLES` inside your Environment.
0 commit comments