Authentication
Send your secret key as Authorization: Bearer sk_live_…. A public key is refused. Test keys (sk_test_…) see the test environment.
curl https://api.pryntid.com/v1/replay/sessions?website=example.com \
-H "Authorization: Bearer sk_live_YOUR_SECRET_KEY" Endpoints
| Method and path | What it does |
|---|---|
GET /v1/replay/sessions | Sessions of a site, 25 per page: website, accountId, userId, days, page, hasErrors, hasRage, hasDead, minFrustration, path, device, country, sort. |
GET /v1/replay/sessions/{id} | One session: pages, errors, failed requests, rage and dead clicks with their offsets, and Py's summary if there is one. |
POST /v1/replay/sessions/{id}/embed | A player link for your own admin: {minutes 1-60, atMs} → {url, token, expiresAt}. See Replay in your own admin. |
POST /v1/replay/sessions/{id}/summary | Py summarizes the session (headline, what happened, friction, outcome). |
GET /v1/replay/sessions/{id}/events | The rrweb events as stored (already masked twice), for your own archive or player. |
GET /v1/replay/recordings | Quick lookup for helpdesks: the latest 10 sessions of a userId, accountId or visitorId, with console links. |
GET /v1/replay/issues | Issues ranked by impact: sessions, users and conversions lost. |
POST /v1/replay/ask | Ask Py about recent sessions: {question, days}. Answers cite sessions as [#id]. |
GET /v1/replay/export | CSV or NDJSON of sessions for your warehouse: website, days, format. |
curl "https://api.pryntid.com/v1/replay/export?website=example.com&days=7&format=ndjson" \
-H "Authorization: Bearer sk_live_YOUR_SECRET_KEY" -o sessions.ndjson Errors and limits
401missing or wrong key ·402Replay is not active on the account ·404not yours, not found or past retention ·422invalid parameter ·429slow down (Retry-After).- Errors come as
{"error": {"code", "message"}}. - Py calls count against your plan's monthly Py limit.
Updated 2026-11-11 · API reference