Notifications

• Register Expo device: This endpoint allows users to register an Expo push token so that the mobile app receives push notifications.
• Unregister Expo device: This endpoint allows users to stop push notifications to an Expo push token or app installation.
• Get Web Push config: This endpoint allows users to check if Web Push is available and to get the VAPID public key.
• Register Web Push subscription: This endpoint allows users to register a browser’s Web Push subscription.
• Get Web Push subscription status: This endpoint allows users to check if a browser installation gets Web Push notifications.
• Unregister Web Push subscription: This endpoint allows users to stop Web Push notifications to a browser installation.
• List notification preferences: This endpoint allows users to get the notification channels that are on for an account.
• Set notification preference: This endpoint allows users to turn a channel on or off for one or more notification types.
• Set notification master preference: This endpoint allows users to turn a channel on or off with the account’s master switch.
• Send test notification: This endpoint allows users to send a test notification on the account’s enabled channels.
• Get notification history: This endpoint allows users to get an account’s recent in-app notifications and unread count.
• Mark notifications seen: This endpoint allows users to mark notifications as seen.

​

Notification types

​

Notification data

​

Preferences

• Pacifica uses a channel only when the channel is on in the master preference and in the type’s preference.
• All channels start off. A missing preference counts as off.
• The master preference doesn’t change the type preferences. You can turn a channel off in the master preference to pause it, and turn it on again later.
• Pacifica picks the channels when it creates a notification. A later preference change doesn’t change notifications that already exist.
• Turning on a type doesn’t backfill notifications for older events.
• The test type uses only the master preference.

​

Mobile push (Expo)

1. On the first install, generate at least 128 random bits. Encode them as a string, for example hexadecimal. Keep this installation key in the device’s secure storage.
2. Get the Expo push token from the Expo SDK.
3. Call Register Expo device with the token, the platform, and the installation key as device_id.
4. Turn on mobile_push in the master preference and for the types that you want.
5. When the user signs out, call Unregister Expo device.

​

Web Push

1. Call Get Web Push config. If enabled is false, hide Web Push in your app. Otherwise, read vapid_public_key.
2. Generate an installation_id of 32 to 64 characters from A-Z, a-z, 0-9, -, and _. Store it where the page and the service worker can both read it, for example IndexedDB.
3. In the browser, call pushManager.subscribe({ userVisibleOnly: true, applicationServerKey: vapid_public_key }).
4. Call Register Web Push subscription with the subscription’s endpoint and keys.
5. Turn on web_push in the master preference and for the types that you want.
6. In the service worker, show each push with showNotification. Use notification_id as the tag.
7. When the page loads, call Get Web Push subscription status. If state is expired or key_rotated, subscribe again and register again.
8. When the user signs out or switches account, call Unregister Web Push subscription.

{
  "version": 1,
  "notification_id": 81234,
  "subscription_id": "3f1c2a7e-9b4d-4e8a-8c2f-6d5b1a0e9f47",
  "title": "Order filled",
  "body": "Your buy BTC order filled at 97000.",
  "data": {
    "notification_type": "order_filled",
    "kind": "order_filled",
    "order_id": "315992721",
    ...
  },
  "created_at_ms": 1716200000000
}

​

History and seen

• Get notification history returns only notifications that Pacifica created with the in_app channel on. Push-only notifications aren’t in the history.
• It returns the 100 newest notifications, newest first. It has no pagination.
• unread_count counts all in-app notifications that aren’t seen. It can be more than 100.
• Mark notifications seen marks the IDs that you send. There is no “mark all” call. Send the IDs that you show.
• Seen state belongs to the account. All the account’s devices and browsers see the same state.

​

Delivery

• Pacifica sends a push only in the first 15 minutes after it creates the notification. After that, it drops the push. The notification stays in the history if in_app was on.
• Pacifica sends a mobile_push notification to every active Expo token on the account. It turns off a token when Expo reports that the device is no longer registered.
• Pacifica sends a web_push notification to every active Web Push subscription on the account. It turns off a subscription when the push service reports that the subscription is gone.
• A push service accepting a push doesn’t mean the device showed it.

​

Signing and limits

• An account keeps up to 10 active Web Push subscriptions. When you register one more, Pacifica turns off the subscription that was registered longest ago.
• An app installation has one active Expo token for each account. When you register a new token with the same device_id, Pacifica turns off the old token.
• The account must exist. An account exists after its first deposit. Other accounts get status 403.
• The standard rate limits apply.