---
title: "Session metrics"
method: GET
path: "/projects/{projectId}/user-testing/scenarios/{scenarioId}/metrics"
tags: ["User testing"]
---

# Session metrics

`GET /projects/{projectId}/user-testing/scenarios/{scenarioId}/metrics`

Volumes, completion and feedback rates over the scenario's sessions.

`404` when the scenario has produced no sessions yet — an empty scenario has no metrics, which is different from metrics that are all zero.

## Query parameters

- `population` 'real' | 'synthetic'

## Response `200`

The metrics.

- ScenarioMetrics — Session metrics for the scenario: volumes, completion and feedback rates, cohort splits. Deliberately UNPINNED. The upstream projection grows with the product and the SDK types it as an open record for the same reason — pinning a field list here would turn every added metric into a spec violation. Read what you recognize and ignore the rest.

## Other responses

- `400` — Malformed body or parameters.
- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/revisions/548954252807/schema)