InvergeDocs

In-app messages

Eligible messages and impression / click events.

SDK-facing (API-key) in-app messages. active returns the messages this person may see — already audience-targeted, A/B-assigned and personalised, plus any pending test send — and whether this is a registered test device. The SDK evaluates triggers + frequency caps locally, then reports impressions/clicks (with the variant). Un-prefixed (/partner/...).

POST /partner/inapp/active

POST 200 x-api-key

Body — ActiveInAppDto

Prop

Type

Request
curl -X POST 'https://services.inverge.net/partner/inapp/active' \
  -H 'x-api-key: nxs_live_xxx' \
  -H 'content-type: application/json' \
  -d '{
      "distinctId": "user_123",
      "deviceKey": "dev_41ab",
      "properties": {}
    }'

POST /partner/inapp/event

POST 202 x-api-key

Body — InAppEventDto

Prop

Type

Request
curl -X POST 'https://services.inverge.net/partner/inapp/event' \
  -H 'x-api-key: nxs_live_xxx' \
  -H 'content-type: application/json' \
  -d '{
      "messageId": "msg_1",
      "type": "impression"
    }'

On this page