Outcome events
Murmle reports what happened as events. Your integration receives them at its webhook_url
or pulls them. Every event has the same envelope:
{
"event_id": "0b7f1c8e-6d1a-4a8e-9f3e-2a6f4b8c9d01",
"event_type": "submission.completed",
"created_at": "2026-10-05T09:14:03.120000+00:00",
"data": { }
}
| Field | Meaning |
|---|---|
event_id | Unique per event and identical on every delivery attempt of it. Your idempotency key. |
event_type | One of the types below. Ignore types you do not know. |
created_at | When the event happened (ISO 8601, UTC). |
data | The event's payload. Ignore fields you do not know. |
submission.completed
A participant who arrived through your launch completed their submission in the run.
{
"external_context": { "context_id": "course-7", "resource_id": "lesson-42" },
"external_user_sub": "u_8f3a2c",
"activity_id": "6a0c...",
"session_id": "b31e...",
"submission_id": "e9d2...",
"status": "completed",
"score_points": 4.0,
"max_points": 5.0,
"score_pct": 80.0,
"passed": null,
"completed_at": "2026-10-05T09:14:03.118000+00:00"
}
| Field | Type | Meaning |
|---|---|---|
external_context.resource_id | string | The linked resource - your resource_id. |
external_context.context_id | string or null | The context stored on the link (external_context_id), if any. |
external_user_sub | string | Your sub for the person. |
activity_id, session_id, submission_id | string | Murmle's ids, for support and deep links. |
status | string | Always completed in v1. |
score_points | number | Points scored. |
max_points | number | Points available across the questions the participant answered. 0 for an unscored activity (a poll, a survey): record a completion, not a grade of zero out of zero. |
score_pct | number | score_points as a percentage of max_points, 0-100. |
passed | boolean or null | Reserved for a pass mark. Murmle has no pass-mark setting today, so it is always null; grade on score_pct yourself. |
completed_at | string or null | ISO 8601, UTC. |
Privacy mode decides whether this event exists
Each run has one of three privacy modes, fixed by the activity's published version:
| Run's privacy mode | submission.completed |
|---|---|
| Identified | Sent, with external_user_sub. The participant was told their answers are recorded against their name. |
| Anonymous to the creator | Not sent. Murmle stores no link from the participant to your sub, by design. |
| Fully anonymous | Not sent. |
A quiz defaults to identified; polls, surveys and Q&A default to anonymous to the creator. If you need outcomes, make sure the activity's creator has not chosen an anonymous mode. No event ever carries a response, free text, an email address or any contact field.
Who receives it
Only the integration that launched the participant. A workspace's general
webhook endpoints subscribed to submission.completed receive the same event
(same event_id) with external_context and external_user_sub removed, signed over that
reduced body. Another integration in the same workspace does not receive it at all.
session.closed
A run that was created by a launch has been closed by its presenter.
{ "session_id": "b31e...", "activity_id": "6a0c..." }
This is a workspace-wide event: every active integration with a webhook_url in the workspace
receives it, whichever integration's launch created the run. It carries no person and no context.
Other event types
session.started and participant.joined are names a workspace's general webhook endpoints can
subscribe to. Murmle does not send them to integrations in v1. Ignore any event type you do
not handle - and acknowledge it with a 2xx, or it will be retried.