Skip to main content
POST
Get session replay metadata

Restrictions

Usage

  • Returns InvalidParameter if the session does not exist, or if it has no replay data recorded (session_has_replay is false).
  • Returns InvalidParameter if no views are found within the session’s time window.
  • Pass ts to disambiguate when a session_id has been reused across different time windows.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json

Look up replay metadata for a single RUM session.

session_id
string
required

RUM session ID.

ts
integer<int64>

Unix timestamp in milliseconds of the session start time. Optional; disambiguates when a session ID has been reused across different time windows.

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

Replay metadata for a session: the application, device, session bounds, and every recorded view.