---
title: "Fetch sessions | Skylar"
description: "Retrieve completed session history for a user from the Skylar Reporting API, with date range and scenario filters."
url: "https://www.getskylar.com/docs/guides/fetch-sessions"
---

# Fetch sessions

Use `GET /v1/users/{userId}/sessions` to retrieve completed session history for a single user, including both Skylar roleplays and ingested real calls.

## Supported query params

-   `page`: positive integer, defaults to `1`
-   `date_from`: inclusive ISO-8601 timestamp lower bound
-   `date_to`: inclusive ISO-8601 timestamp upper bound
-   `scenario_id`: exact scenario identifier match

## Request

```
curl --request GET \
  --url "$REPORTING_API_BASE_URL/v1/users/user-123/sessions?page=1&date_from=2026-04-01T00:00:00.000Z&date_to=2026-04-30T23:59:59.999Z" \
  --header "Authorization: Bearer $SKYLAR_REPORTING_API_KEY"
```

## Success response

```
{
  "data": [
    {
      "session_id": "conversation-123",
      "completed_at": "2026-04-08T10:00:00.000Z",
      "scenario_id": "scenario-001",
      "scenario_name": "Discovery Call",
      "session_type": "roleplay"
    }
  ],
  "pagination": {
    "page": 1,
    "page_size": 100,
    "has_next_page": false
  }
}
```

## Integration notes

-   Use `scenario_id` when you need one scenario family only.
-   The response is paginated. Keep incrementing `page` while `has_next_page` is `true`.
-   `session_type` tells you whether the record came from a native Skylar roleplay or an ingested `real_call`.
-   `completed_at` can be `null`, so do not assume every record has a timestamp.

## Related links

-   [Ingest real calls](https://www.getskylar.com/docs/guides/ingest-real-calls)
-   [Pagination and errors](https://www.getskylar.com/docs/guides/pagination-and-errors)
-   [Fetch assessments](https://www.getskylar.com/docs/guides/fetch-assessments)
-   [API reference](https://www.getskylar.com/docs/api-reference)
