about summary refs log tree commit diff
diff options
context:
space:
mode:
authorEugen Rochko <eugen@zeonfederated.com>2017-01-29 12:55:12 +0100
committerEugen Rochko <eugen@zeonfederated.com>2017-01-29 12:55:12 +0100
commitca8a9d5941ed9e5ae11087a296237fdddb5d45d7 (patch)
treee5057e4acf618b8e53180297227c2f8a661ee4b2
parentfe9306f346f6c9ee875859beba282f8f06e524da (diff)
Fix JSON formatting in docs
-rw-r--r--docs/Using-the-API/Push-notifications.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Using-the-API/Push-notifications.md b/docs/Using-the-API/Push-notifications.md
index 3ce3e36e2..746bf65ef 100644
--- a/docs/Using-the-API/Push-notifications.md
+++ b/docs/Using-the-API/Push-notifications.md
@@ -11,7 +11,7 @@ When the app obtains/refreshes a registration ID from Firebase, it needs to send
 The push notifications will be triggered by the notifications of the type you can normally find in `/api/v1/notifications`. However, the push notifications will not contain any inline content. They will contain JSON data of this format ("12" is an example value):
 
 ```json
-{ notification_id: 12 }
+{ "notification_id": 12 }
 ```
 
 Your app can then retrieve the actual content of the notification from the `/api/v1/notifications/12` API endpoint.