Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Created faq #67

Merged
merged 3 commits into from
Jan 10, 2024
Merged

Created faq #67

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
4bcab37
Created faq
devthedevel Jan 9, 2024
c5a1ad9
Fixed sidebar positioning of faq
devthedevel Jan 9, 2024
031e78e
PR comments
devthedevel Jan 10, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/reference/js-client.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Loading