---
title: "Find all sessions in a test"
method: GET
path: "/api/v2/sessionResults"
tags: ["General Session Data"]
---

# Find all sessions in a test

`GET /api/v2/sessionResults`

Returns a paginated list of summaries for each completed session in a test. Each summary includes the session ID, status, and timestamps. 

  In the response, sessions are sorted in descending order, i.e., from newest to oldest.
  
  _Compatibility:_
  - All tests with the "STUDYV2" type are compatible. These include tests with the following product types:
    - "SURVEY" (survey)
    - "LIVE_CONVERSATION" (non-classic live conversation)
    - "NON_THINK_OUT_LOUD" (interaction test)
    - "THINK_OUT_LOUD" (think-out-loud test) 
  - Go to [How to Obtain a Test ID (UUID)](https://developer.usertesting.com/docs/how-to-obtain-a-testid-uuid) for details.
  
  _Best practices:_
  - Always use pagination query parameters (_limit_ and _offset_) along with the appropriate logic to ensure all sessions are retrieved.
  - Use the response data from _limit_, _offset_, and _totalCount_ in the _meta.pagination_ property to calculate the number of pagination iterations (API requests) needed to collect all sessions in the test.
  
  _Use case examples:_
  - For an example on near real-time polling, go to [Stream Insights into Slack or Jira](https://developer.usertesting.com/v2.0/docs/stream-insights-into-slack-or-jira).
  - For an example on how to add session summaries into an automated research data pipeline, go to [Create an Automated Pipeline](https://developer.usertesting.com/v2.0/docs/tutorial).

## Query parameters

- `testId` string, uuid, required
- `limit` number
- `offset` number

## Response `200`

Session summaries successfully retrieved.

- SessionSummaryResultsResponseDto
  - `testId` string, uuid, required — ID of the test queried for session summaries.
  - `sessions` SessionSummaryResultItemDto[], required — Collection of session summaries.
    - `sessionId` string, uuid, required — ID of the session.
    - `audienceId` string, uuid, nullable — Identifier of the audience that the session participant belongs to. Null if session has no assigned audience.
    - `status` string, required — Session completion status.
    - `startTime` string, date-time, required — Timestamp representing when the session started. UTC timezone. ISO 8601 format.
    - `finishTime` string, date-time, nullable — Timestamp representing when the session finished. UTC timezone. ISO 8601 format.
  - `meta` SessionSummaryResultsMetaDto, required
    - `pagination` SessionSummaryPaginationDto, required
      - `limit` number, required — Maximum number of sessions returned in the result set.
      - `offset` number, required — Number of sessions skipped before starting to collect the result set.
      - `totalCount` number, required — Total number of sessions within the test.

## Other responses

- `400` — Bad request. The offset must be between 0-10000 and limit must be between 1-500.
- `401` — Missing or invalid access token.
- `404` — Test not found.
- `429` — Too many requests. Maximum of 10 requests per minute.

---

[API](https://skmtc.dev/usertesting/apis/results-api.md) · [All operations](https://skmtc.dev/usertesting/apis/results-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/usertesting/results-api/revisions/8124f6985018/schema)