v1

latestOpenAPI 3.0.1Apache 2.02026-08-063494581.6 MB
device_MultiOS Remote Viewer

Get RemoteViewer Activity Feed for the tenant

Retrieves a paginated, filterable feed of Remote Viewer sessions across the tenant.

Each entry represents one Remote Viewer session, including the device it targeted, its current state, video quality, duration, and who initiated it. Supports filtering by state, video quality, device name, and the user who created the session.

About Remote Viewer Activity Feed

Remote Viewer sessions move through INITIATED, ACKNOWLEDGED, ACTIVE, and a terminal TERMINATED or FAILED state. This feed gives a tenant-wide, auditable view of who has remotely viewed which devices, how long each session lasted, and whether it completed successfully, spanning the multi-OS Remote Viewer feature rather than any single platform.

Key Fields / Query Parameters

states — filters by one or more session states, comma-separated

created_by — filters sessions by the user who initiated them

device_name — searches sessions by device name

ordering — orders results, defaults to -created_at (most recent first)

Common Use Cases

Auditing who accessed a given device through Remote Viewer and when

Reviewing failed or unusually long Remote Viewer sessions across the fleet

Investigating support activity on a specific device by filtering on device_name

Best Practices

Filter by states to separate completed sessions from ones that failed or never became active

Use created_by when auditing an individual support agent's Remote Viewer activity

Workflow

Call this endpoint with the filters relevant to your audit or investigation

Review session state and duration for each result

Use the session_id to correlate with support tickets or other internal records if needed

get/v2/rv-activity-feed/

Query parameters

limitinteger
offsetinteger
states'INITIATED' | 'ACKNOWLEDGED' | 'ACTIVE' | 'TERMINATED' | 'FAILED'

List API supports comma separated states.

video_qualities'STANDARD' | 'DATA_SAVER'

To allow filtering sessions list by comma separated video qualities

reasonstring

To allow searching sessions list by reason

created_bystring

To allow filtering sessions list by created by

device_namestring

To allow searching sessions list by device name

ordering'created_at' | 'updated_at' | 'device_name' | 'duration' | 'state' | 'reason' | 'video_quality' | 'created_by'

To allow ordering sessions list by created_at, updated_at, device_name, duration, state, reason, video_quality and created_by.

duration_ltstring duration

Duration less than filter. The time duration (in ISO 8601 duration format) of only a valid elapsed session, i.e., sessions that have moved from ACTIVE state (where session start-time can be captured) to TERMINATED or FAILED state (where the session end-time can be captured).

Example:duration_lt=PT10M30S
duration_ltestring duration

Duration less than or equal to filter. The time duration (in ISO 8601 duration format) of only a valid elapsed session, i.e., sessions that have moved from ACTIVE state (where session start-time can be captured) to TERMINATED or FAILED state (where the session end-time can be captured).

Example:duration_lte=PT10M30S
duration_gtstring duration

Duration greater than filter. The time duration (in ISO 8601 duration format) of only a valid elapsed session, i.e., sessions that have moved from ACTIVE state (where session start-time can be captured) to TERMINATED or FAILED state (where the session end-time can be captured).

Example:duration_gt=PT10M30S
duration_gtestring duration

Duration greater than or equal to filter. The time duration (in ISO 8601 duration format) of only a valid elapsed session, i.e., sessions that have moved from ACTIVE state (where session start-time can be captured) to TERMINATED or FAILED state (where the session end-time can be captured).

Example:duration_gte=PT10M30S
created_at_ltstring date-time

Created at less than filter. Datetime format must be in "YY-MM-DDTHH:mm:ss.fffffffffZ".

Example:created_at_lt=2023-10-01T12:00:00Z
created_at_gtstring date-time

Created at greater than filter. Datetime format must be in "YY-MM-DDTHH:mm:ss.fffffffffZ".

Example:created_at_gt=2023-10-01T12:00:00Z
created_at_ltestring date-time

Created at less than or equal to filter. Datetime format must be in "YY-MM-DDTHH:mm:ss.fffffffffZ".

Example:created_at_lte=2023-10-01T12:00:00Z
created_at_gtestring date-time

Created at greater than or equal to filter. Datetime format must be in "YY-MM-DDTHH:mm:ss.fffffffffZ".

Example:created_at_gte=2023-10-01T12:00:00Z
updated_at_ltstring date-time

Updated at less than filter. Datetime format must be in "YY-MM-DDTHH:mm:ss.fffffffffZ".

Example:updated_at_lt=2023-10-01T12:00:00Z
updated_at_gtstring date-time

Updated at greater than filter. Datetime format must be in "YY-MM-DDTHH:mm:ss.fffffffffZ".

Example:updated_at_gt=2023-10-01T12:00:00Z
updated_at_ltestring date-time

Updated at less than or equal to filter. Datetime format must be in "YY-MM-DDTHH:mm:ss.fffffffffZ".

Example:updated_at_lte=2023-10-01T12:00:00Z
updated_at_gtestring date-time

Updated at greater than or equal to filter. Datetime format must be in "YY-MM-DDTHH:mm:ss.fffffffffZ".

Example:updated_at_gte=2023-10-01T12:00:00Z

Response

Success

Example response

{
  "content": {
    "results": [
      {
        "duration": "PT10M30S"
      }
    ]
  }
}