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 view with replay data is found between the session start and 4 hours after its recorded end.
  • ts must equal the session’s start time exactly (Unix milliseconds); any other value makes the session lookup miss and returns InvalidParameter.
  • If the session belongs to a private application the caller cannot access, the call returns AccessDenied (“You do not have permission to access this application”).
  • All timestamps are client times; no clock-skew correction is applied (server_time_delta is always 0).

Authorizations

app_key
string
query
required

APP Key created in the Flashduty console under My → APP Key. Send it as the app_key query parameter or in the Fd-App-Key request header. Its effective access is the intersection of the key's permission scope and the creator's current role permissions. Keep it secret.

Body

application/json

Look up replay metadata for a single RUM session.

session_id
string
required

RUM session ID (the session.id attribute on RUM events).

ts
integer<int64>

Session start time, Unix milliseconds. Optional. When set, it must match the session's start exactly; use it to pick one session when a session_id was reused.

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

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