An event is a signal from your application that triggers rule evaluation for a participant. Events process asynchronously and are deduplicated byDocumentation Index
Fetch the complete documentation index at: https://docs.scrip.dev/llms.txt
Use this file to discover all available pages before exploring further.
idempotency_key within a program.
Endpoints
- Ingest: submit a single event or a batch of up to 100
- Get: retrieve an event by
idoridempotency_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
FAILEDevent for reprocessing
For usage patterns and examples, see the Event Processing guide.