The Events API ingests customer events into the platform’s event bus. Events are evaluated against active trigger rules in real time and published to a per-tenant Redis Stream. Supports single events and batches of up to 100. Rate limited to 500 requests/min. Editor or Admin.
Trigger evaluation does not depend on the stream. The route calls the trigger
engine directly and treats the stream publish as non-critical, so a streamId of
null never means a missed trigger.No stream consumer ships with the platform. events:<tenantId> is a fan-out
sink for your own consumers. Because nothing reads it by default, each stream is
capped with MAXLEN ~ (EVENT_STREAM_MAXLEN, default 10000 entries) — before
2026-08-15 it was uncapped and grew until Redis ran out of memory. If you attach a
consumer, acknowledge each message after processing it so Redis’ pending-entries
list can redeliver on a crash.
POST /api/v1/events
Ingest one or more customer events.
Request Body — Single Event
Request Body — Batch
Send an array of event objects (max 100 per batch).
Example — Single Event
Example — Batch
Response (202)
Events are automatically evaluated against active Trigger Rules. If a trigger’s conditions match, it fires its configured action (e.g., journey enrollment, webhook). 
