S2S Conversations

Set conversation events

Attach an event log snapshot to the conversation — the same events Gleap.trackEvent() buffers in the SDK flow and attaches when a conversation is created. Scoped to this conversation only (not the contact), so events from other sessions never mix in. Shown to agents in the conversation's "Logs" panel. Each call replaces the previous snapshot (max 500 events, 2 MB). Not delivered via webhooks or the stream. For contact-level events that drive outbound rules, use POST /contacts/{userId}/events instead.

PUT

https://api.gleap.io/v3/s2s/conversations/{conversationId}/events

Authorizations

Authorizationstring · headerrequired

Bearer authentication header of the form Bearer <token>.

Path parameters

conversationIdstringrequired

Bodyapplication/jsonrequired

eventsobject[]required

Snapshot of the events that led up to this conversation (max 500 entries, 2 MB). Replaces any previous snapshot for this conversation.

Show child attributes

namestringrequired

Event name, e.g. "screen_opened" or "pageView".

datestring

ISO timestamp of when the event happened; defaults to now.

dataany

Arbitrary event payload (flat key→value object).

Response

No Content

Updated November 1, 2026

curl --request PUT \
  --url 'https://api.gleap.io/v3/s2s/conversations/{conversationId}/events' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "events": [
    {
      "name": "<name>"
    }
  ]
}'

No example in the spec.