Update README.md

Author: github-actions[bot]

README.md

@@ -31,10 +31,11 @@ endpoint restrictions, placeholders, flexible configuration
 - [Getting Started](#getting-started)
 - [Setup](#setup)
 - [Usage](#usage)
-- [Best Practices](#security-best-practices)
+- [Best Practices](#best-practices)
 - [Configuration](#configuration)
   - [Endpoints](#endpoints)
   - [Variables](#variables)
+  - [Data Aliases](#data-aliases)
   - [Message Templates](#message-templates)
 - [Contributing](#contributing)
 - [Support](#support)
@@ -66,9 +67,10 @@ services:
     container_name: secured-signal
     environment:
       API__URL: http://signal-api:8080
-      SETTINGS__VARIABLES__RECIPIENTS: "[+123400002, +123400003, +123400004]"
+      SETTINGS__VARIABLES__RECIPIENTS:
+        '[+123400002, +123400003, +123400004]'
       SETTINGS__VARIABLES__NUMBER: "+123400001"
-      API__TOKENS: "[LOOOOOONG_STRING]"
+      API__TOKENS: '[LOOOOOONG_STRING]'
     ports:
       - "8880:8880"
     restart: unless-stopped
@@ -100,9 +102,10 @@ services:
     container_name: secured-signal
     environment:
       API__URL: http://signal-api:8080
-      SETTINGS__VARIABLES__RECIPIENTS: "[+123400002,+123400003,+123400004]"
+      SETTINGS__VARIABLES__RECIPIENTS:
+        '[+123400002,+123400003,+123400004]'
       SETTINGS__VARIABLES__NUMBER: "+123400001"
-      API__TOKENS: "[LOOOOOONG_STRING]"
+      API__TOKENS: '[LOOOOOONG_STRING]'
     labels:
       - traefik.enable=true
       - traefik.http.routers.signal-api.rule=Host(`signal-api.mydomain.com`)
@@ -238,31 +241,24 @@ curl -X POST -H "Content-Type: application/json" -H "Authorization: Bearer API_T
 
 #### Placeholders
 
-If you are not comfortable / don't want to hardcode your Number for example and/or Recipients in you, may use **Placeholders** in your Request. See [Custom Variables](#variables).
+If you are not comfortable / don't want to hardcode your Number for example and/or Recipients in you, may use **Placeholders** in your Request.
 
-These Placeholders can be used in the Request Query or the Body of a Request like so:
+You can use [**Variable**](#variables) `{{.NUMBER}}` Placeholders and **Body** Placeholders `{{@data.key}}`.
 
-**Body**
+| Type  | Example                                                          |
+| :---- | :--------------------------------------------------------------- |
+| Body  | `{"number": "{{ .NUMBER }}", "recipients": "{{ .RECIPIENTS }}"}` |
+| Query | `http://sec-signal-api:8880/v1/receive/?@number={{.NUMBER}}`     |
+| Path  | `http://sec-signal-api:8880/v1/receive/{{.NUMBER}}`              |
+
+You can also combine them:
 
 ```json
 {
-	"number": "{{ .NUMBER }}",
-	"recipients": "{{ .RECIPIENTS }}"
+	"content": "{{.NUMBER}} -> {{.RECIPIENTS}}"
 }
 ```
 
-**Query**
-
-```
-http://sec-signal-api:8880/v1/receive/?@number={{.NUMBER}}
-```
-
-**Path**
-
-```
-http://sec-signal-api:8880/v1/receive/{{.NUMBER}}
-```
-
 #### KeyValue Pair Injection
 
 In some cases you may not be able to access / modify the Request Body, in that case specify needed values in the Request Query:
@@ -272,7 +268,7 @@ In some cases you may not be able to access / modify the Request Body, in that c
 In order to differentiate Injection Queries and _regular_ Queries
 you have to add `@` in front of any KeyValue Pair assignment.
 
-Supported types include **strings**, **ints** and **arrays**. See [Formatting](#string-to-type).
+Supported types include **strings**, **ints**, **arrays** and **json dictionaries**. See [Formatting](#string-to-type).
 
 ## Best Practices
 
@@ -295,20 +291,28 @@ This example config shows all of the individual settings that can be applied:
 
 ```yaml
 # Example Config (all configurations shown)
+service:
+  port: 8880
 
 api:
-  port: 8880
   url: http://signal-api:8080
   tokens: [token1, token2]
 
-logLevel: INFO
+logLevel: info
 
 settings:
+  messageTemplate: |
+    You've got a Notification:
+    {{}} 
+    At {{.timestamp}} on {{.date}}.
+    Send using {{.NUMBER}}.
+
   variables:
     number: "+123400001"
     recipients: ["+123400002", "group.id", "user.id"]
 
-  messageAliases: [{ alias: "msg", score: 100 }]
+  dataAliases: 
+    "": [{ alias: "msg", score: 100 }]
 
   blockedEndpoints:
     - /v1/about
@@ -437,9 +441,61 @@ settings:
     recipients: ["+123400002", "group.id", "user.id"]
 ```
 
+### Message Templates
+
+To customize the `message` attribute you can use **Message Templates** to build your message by using other Body Keys and Variables.
+Use `messageTemplate` to configure:
+
+```yaml
+settings:
+  messageTemplate: |
+    Your Message:
+    {{@message}}.
+    Sent with Secured Signal API.
+```
+
+Use `{{@data.key}}` to reference Body Keys and `{{.KEY}}` for Variables.
+
+### Data Aliases
+
+To improve compatibility with other services Secured Signal API provides **Data Aliases** and a built-in `message` Alias.
+
+<details>
+<summary><strong>Default `message` Aliases</strong></summary>
+
+| Alias        | Score | Alias            | Score |
+| ------------ | ----- | ---------------- | ----- |
+| msg          | 100   | data.content     | 9     |
+| content      | 99    | data.description | 8     |
+| description  | 98    | data.text        | 7     |
+| text         | 20    | data.summary     | 6     |
+| summary      | 15    | data.details     | 5     |
+| details      | 14    | body             | 2     |
+| data.message | 10    | data             | 1     |
+
+</details>
+
+Secured Signal API will pick the best scoring Data Alias (if available) to extract set the Key to the correct Value from the Request Body.
+
+Data Aliases can be added by setting `dataAliases` in your config:
+
+```yaml
+settings:
+  dataAliases:
+    "@message":
+      [
+        { alias: "msg", score: 80 },
+        { alias: "data.message", score: 79 },
+        { alias: "array[0].message", score: 78 },
+      ]
+    ".NUMBER": [{ alias: "phone_number", score: 100 }]
+```
+
+Use `@` for aliasing Body Keys and `.` for aliasing Variables.
+
 ### Port
 
-To change the Port which Secured Signal API uses, you need to set `server.port` in your config. (default: `8880`)
+To change the Port which Secured Signal API uses, you need to set `service.port` in your config. (default: `8880`)
 
 ### Log Level