Skip to main content
App Notifications in Replyke are in-app records — they appear in a notification feed inside your app. To deliver push notifications (iOS APNs, Android FCM) when users are not actively using the app, you can configure a webhook that fires whenever a notification is created.

​
How It Works

1

Configure a webhook URL in the dashboard

In your Replyke project dashboard, go to Settings → Webhooks and add a webhook URL pointing to your backend endpoint. Select the App Notification Created event.
2

Receive the event on your backend

When Replyke creates an app notification, it sends an HTTP POST to your webhook URL with a JSON payload describing the notification:
{
  "type": "app-notification.created",
  "projectId": "your-project-id",
  "data": {
    "projectId": "your-project-id",
    "userId": "recipient-user-id",
    "type": "entity-comment",
    "action": "open-comment",
    "metadata": {
      "entityId": "...",
      "commentId": "...",
      "initiatorId": "...",
      "initiatorName": "Alice"
    }
  }
}
3

Look up the recipient's push token

Use data.userId to look up the FCM or APNs token stored in your own database for that user.
4

Send the push notification

Use your push provider (Firebase Admin SDK, APNs, Expo Push, etc.) to send a push notification to the device. Build the message text using data.type and data.metadata from the webhook payload.

​
Payload Fields

FieldTypeDescription
typestringAlways "app-notification.created"
projectIdstringThe Replyke project ID
data.projectIdstringThe Replyke project ID (repeated inside data)
data.userIdstringThe recipient’s user ID
data.typestringThe notification type (e.g., "entity-comment")
data.actionstringNavigation hint for the push tap action
data.metadataobjectType-specific data — see Notification Templates for fields per type
You are responsible for managing and storing push tokens in your own backend. Replyke does not store device tokens.