Skip to main content

Pulling outcomes

If you cannot or would rather not expose an HTTPS endpoint, fetch the same events yourself. Pulling and webhooks read one queue: an event is the same object, with the same event_id, the same data and the same privacy rules, whichever way it reaches you. You may use either or both; neither affects the other.

GET {MURMLE}/api/public/v1/integrations/{integration_id}/outcomes?after=<cursor>&limit=<n>
Authorization: Bearer pk_<prefix>_<secret>

The key​

A workspace API key with the outcomes:read scope that is bound to your integration. A workspace owner mints it in Console > Integrations > API keys, ticking outcomes:read and choosing your integration. Alternatively, the registration key you registered with can carry outcomes:read as well, in which case it is bound to your integration automatically. A key reads one integration's events in one workspace, and nothing else.

Parameters​

ParameterMeaning
afterOptional. The next_cursor from your previous call. Omit it on the first call to start from the oldest retained event.
limitOptional. 1-200 events per page, default 50.

Response​

200:

{
"items": [
{
"event_id": "0b7f1c8e-6d1a-4a8e-9f3e-2a6f4b8c9d01",
"event_type": "submission.completed",
"created_at": "2026-10-05T09:14:03.120000+00:00",
"data": { "external_user_sub": "u_8f3a2c", "score_pct": 80.0 }
}
],
"next_cursor": "MjAyNi0xMC0wNVQwOToxNDowMy4xMjAwMDArMDA6MDB8MGI3ZjFj...",
"has_more": false
}

Which events. Exactly the ones your webhook would receive: submission.completed for participants your launches brought in, and the workspace-wide session.closed. The privacy rules in Outcome events apply unchanged - an anonymous run produces no submission.completed, so there is nothing to pull for it. Events from before your integration was registered are not included.

Cursor semantics​

  • Opaque. Store next_cursor as a string and send it back as after. Do not parse or build one; a cursor Murmle did not issue is refused with 422.
  • Ordered and stable. Events come oldest first, in one fixed order. Paging with the cursor returns each retained event once; it never skips one and never repeats one.
  • Reading acknowledges nothing. Pulling marks nothing delivered. Persist the cursor after you have processed a page; if you crash before that, pull the same page again and deduplicate on event_id, exactly as for webhooks.
  • Caught up. When there is nothing new, items is empty and next_cursor is the cursor you sent. Keep it and poll again later - once a minute is plenty. The limit is 60 calls per minute per key, after which you get 429.
  • has_more: true means call again straight away. A page may hold fewer than limit items even then: Murmle skips other integrations' events while it reads, and the cursor still moves past them.
  • A short delay. An event becomes pullable about 5 seconds after it happens, so a page boundary can never pass an event whose transaction had not yet committed.

Retention: pull within the window​

Events are deleted 30 days after they happened by default (the deployment's operator sets the period). That applies to pulled events too. An integration that polls less often than that loses events for good. Murmle's results and exports remain the system of record.

Errors​

StatusMeaning
401No key, or the key is unknown, wrong or revoked.
403The key lacks outcomes:read. The detail names the scope.
404The key is not bound to this integration. Deliberately the same as "no such integration", so a key cannot probe for other integrations' ids.
409The integration is awaiting approval, or disabled.
422after is not a cursor Murmle issued, or limit is out of range.
429Rate limited; slow down and retry. Every call counts towards the limit, including ones refused with 404.