App events

Send a silent track or screen event over HTTP so trigger rules can react; the REST twin of the realtime track and screen frames.

POST /v1/events
Authorization: Bearer kst_…
Content-Type: application/json

{ "name": "geofence_entered", "properties": { "store": "Shibuya" } }

or for a screen view:

{ "screen": "checkout" }

200:

{ "triggered": [ { "triggerId": "trg_01J8FAKE_geofence", "conversationId": "conv_…" } ] }

triggered is empty when no enabled rule matched. When a rule matches, the runtime reuses the user’s latest open conversation (or creates one without a greeting), emits trigger.fired, and then the rule’s reactions: an app.notify event (and a push when appropriate) and/or a prepared assistant turn. The events reach the app over its socket or on the next event poll.

Rules are evaluated per environment, audience and frequency cap, with an optional condition over properties, context and user. See Triggers.

The Flutter SDK sends these as track and screen frames on the socket when connected and falls back to this endpoint otherwise.