InvergeDocs

Sessions & identity

Identify people and keep the journey session that every other product correlates into.

SDK-facing (API-key) ingestion for the sessions spine. identify upserts the end-user; track resolves/starts the active session and returns a sessionId the SDK stamps on its telemetry. Un-prefixed (/partner/...).

POST /partner/sessions/identify

POST 201 x-api-key

Body — IdentifyDto

Prop

Type

Request
curl -X POST 'https://services.inverge.net/partner/sessions/identify' \
  -H 'x-api-key: nxs_live_xxx' \
  -H 'content-type: application/json' \
  -d '{
      "distinctId": "user_123"
    }'

POST /partner/sessions/track

POST 201 x-api-key

Headers

Prop

Type

Body — TrackDto

Prop

Type

Request
curl -X POST 'https://services.inverge.net/partner/sessions/track' \
  -H 'x-api-key: nxs_live_xxx' \
  -H 'content-type: application/json' \
  -d '{
      "distinctId": "user_123",
      "email": "string",
      "name": "order_placed"
    }'

On this page