PR comments

notificationapi-com · Jan 10, 2024 · 031e78e · 031e78e
1 parent c5a1ad9
commit 031e78e
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 11 deletions.
diff --git a/docs/faq/_category_.json b/docs/faq/_category_.json
diff --git a/docs/faq/faq.md b/docs/faq/faq.md
diff --git a/docs/reference/js-client.md b/docs/reference/js-client.md
@@ -374,3 +374,11 @@ notificationapi.showUserPreferences();
 | id\*      | string | The unique ID of the user in your system.                    |
 | email     | string | The email of the user.                                       |
 | phone     | string | The phone number of the user. Expected format: +15554443333. |
+
+## Frequently Asked Questions (FAQ)
+
+### Why Can I Not Send Notifications from a Front-end SDK?
+
+NotificationAPI back-end SDKs require your `clientId` and `clientSecret` keys that are unique to your account. If anyone else obtained your keys then they would be able to edit or delete your notifications, and be able to send requests to NotificationAPI from your account. This is a security risk to you and your clients. 
+
+To better protect you, the NotificationAPI front-end SDKs do not allow _sending_ notifications: they only allow _receiving_ notifications. If you require sending notifications from your front-end, it is recommended to use a NotificationAPI back-end SDK on your back-end and expose an API for your front-end.