Session ReplaysGet a session recording

Get a session recording

Return the full rrweb event stream for one session (DOM + console + network), concatenated in order. Feed data.events straight into an rrweb player such as rrweb-player — pinned to exactly 2.0.0-alpha.20 (streams are rrweb 2.1.0; the stable 2.0.x/2.1.x rrweb-player ESM builds ship without the replay engine and crash on load).

Tabs. A session can span several page loads (windows), and a visitor with two tabs open records two windows at the same time. An rrweb player has one frame, so two overlapping windows played together corrupt each other: one tab's DOM changes land on the other tab's page. tracks groups window ids that never overlap and can share a player. One track (the usual case) means data.events plays as-is. More than one means overlapping: true: fetch and play each track separately with ?window_id=.

curl -X GET "https://mythic-analytics.gulp.workers.dev/client/v1/data/replays/example_string?location_id=example_string&window_id=example_string" \
  -H "Content-Type: application/json" \
  -H "X-Location-Id: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "success": true,
  "data": {
    "session_id": "example_string",
    "events": [
      {}
    ],
    "windows": [
      {
        "window_id": "example_string",
        "started_at": 42,
        "ended_at": 42,
        "event_count": 10,
        "href": "example_string",
        "width": 123,
        "height": 42
      }
    ],
    "tracks": [
      [
        "0f4954dc-..."
      ],
      [
        "e3a27165-..."
      ]
    ],
    "overlapping": true
  }
}
GET
/replays/{sessionId}
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need replays:read; the session logs route, and include=logs on the timeline, also need logs:read. See Using an mcp_ key over HTTP.

Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need replays:read; the session logs route, and include=logs on the timeline, also need logs:read. See Using an mcp_ key over HTTP.
path
sessionIdstring
Required

The session id from the list endpoint.

query
location_idstring

Alternative to the X-Location-Id header for agency (ak_) keys. Ignored for secret (sk_) keys.

query
window_idstring

Comma-separated window ids (from tracks or windows). Returns only those windows' events. Omit for the whole session.

header
X-Location-Idstring

Location to scope the request to. Required for agency (ak_) keys. Ignored for secret (sk_) keys, which resolve their own location.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. Agency key (ak_) or location secret key (sk_) as a bearer token. Format: Bearer ak_... or Bearer sk_.... Scoped keys (mcp_) are accepted too and need replays:read; the session logs route, and include=logs on the timeline, also need logs:read. See Using an mcp_ key over HTTP.

Path Parameters

sessionIdstring
Required

The session id from the list endpoint.

Query Parameters

location_idstring

Alternative to the X-Location-Id header for agency (ak_) keys. Ignored for secret (sk_) keys.

window_idstring

Comma-separated window ids (from tracks or windows). Returns only those windows' events. Omit for the whole session.

Headers

X-Location-Idstring

Location to scope the request to. Required for agency (ak_) keys. Ignored for secret (sk_) keys, which resolve their own location.

Responses

successboolean
dataobject