Skip to main content
An event is a signal from your application that triggers rule evaluation for a participant. Events process asynchronously and are deduplicated by idempotency_key within a program. Ingestion confirms receipt, not that processing will complete.

​
Endpoints

  • Ingest: submit a single event or a batch of up to 100
  • Get: retrieve an event by id or idempotency_key
  • Impact: get the full causal chain for a processed event (rule evaluations, journal entries, state changes, balance impact)
  • List: filter events by program, participant, status, event type, and time window
  • Retry: requeue a FAILED event for reprocessing
For usage patterns and examples, see the Event Processing guide.