Get event impact
Returns the full causal chain for a processed event: rule evaluations, journal entries with postings, state changes, and per-entity balance impact.
rule_set_id. State changes include the rule_id that caused them, linking every tag, counter, attribute, and tier change back to the specific rule.
The evaluation trace is sparse. Clean false conditions have no row, and later rules in the same set that were not reached after a successful stop_after_match have no row. Processing still continues with the next set. This endpoint has no include_skipped filter and returns all recorded evaluation rows, including SKIPPED_ERROR and SKIPPED_TIMEOUT.
The balance_impact array aggregates all postings into net changes per entity, asset, and bucket. Zero-sum entries (where credits and debits cancel out) are omitted. System accounts (SYSTEM_ISSUANCE, SYSTEM_BREAKAGE, SYSTEM_REDEMPTION) appear as counterparties to participant and group movements.
PENDING or PROCESSING status return the event metadata with empty arrays for all impact fields. This endpoint is most useful once the event reaches COMPLETED or FAILED.For usage patterns and examples, see the Event Processing guide.Authorizations
API key passed in the X-API-Key header.
Path Parameters
Event ID
Response
Event impact details
Net balance impact per entity/asset/bucket
When this event was created
"2024-01-15T10:30:00Z"
Machine-readable failure code for a terminal FAILED event, when one is available (e.g. program_not_found, participant_suspended, participant_inactive). NULL when the event did not fail or the failure carried no stable code.
"program_not_found"
Error details if the event failed during processing
"rule condition evaluation failed"
Original event data payload
When the event occurred (from the ingestion request)
"2024-01-15T10:30:00Z"
Event type: EXTERNAL (API-ingested) or SYSTEM (internally generated)
"EXTERNAL"
Your system's identifier for the participant (the value provided at ingestion)
"user_abc123"
Unique identifier for this event
"550e8400-e29b-41d4-a716-446655440000"
Client-provided unique key for deduplication
"order-12345-completed"
Journal entries created by this event with their double-entry postings
Participant UUID, resolved from external_id if one was provided at ingestion
"550e8400-e29b-41d4-a716-446655440002"
When the event finished processing (null while pending or processing)
"2024-01-15T10:30:02Z"
Program this event belongs to
"550e8400-e29b-41d4-a716-446655440001"
When Scrip received the event
"2024-01-15T10:30:01Z"
Reward recipient UUID, if different from the triggering participant
"550e8400-e29b-41d4-a716-446655440003"
Recorded rule-evaluation rows for this event. Rules whose conditions cleanly evaluate to false are not recorded; later rules in the same set after a successful stop_after_match are not evaluated or recorded.
State changes (tags, counters, attributes, tiers) caused by this event
Processing status: PENDING, PROCESSING, COMPLETED, or FAILED
"COMPLETED"
When this event was last updated
"2024-01-15T10:30:00Z"