---
title: "Start a browser session replay recording"
method: POST
path: "/browsers/{id}/replays"
tags: ["Browser Replays"]
---

# Start a browser session replay recording

`POST /browsers/{id}/replays`

Start recording the browser session and return a replay ID.

## Path parameters

- `id` string, required

## Request body

- object
  - `framerate` integer — Recording framerate in fps. Values above 20 require GPU to be enabled on the browser session.
  - `max_duration_in_seconds` integer — Maximum recording duration in seconds.
  - `record_audio` boolean — Record audio in addition to video. When false (the default), the recording is video-only.

## Response `201`

Recording started successfully.

- BrowserReplay — Information about a browser replay recording.
  - `replay_id` string, required — Unique identifier for the replay recording.
  - `started_at` string, date-time, nullable — Timestamp when replay started
  - `finished_at` string, date-time, nullable — Timestamp when replay finished
  - `replay_view_url` string — URL for viewing the replay recording.

## Other responses

- `400` — Bad Request – invalid input
- `403` — Forbidden – insufficient permissions or plan
- `404` — Resource not found
- `409` — Conflict – resource already exists
- `500` — Internal Server Error

---

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