Recording status API

Your capture script calls this before recording and periodically during a session. If authorized is false, stop capturing immediately.

GET | POST /api/public/v1/recording/status

Auth: Authorization: Bearer rmp_… (or X-Api-Key). POST body may include {"new_session": true} to count a session.

curl -X POST https://<your-app>/api/public/v1/recording/status \
  -H "Authorization: Bearer rmp_0a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b" \
  -H "Content-Type: application/json" \
  -d '{"new_session": true}'

200 - authorized

{
  "authorized": true,
  "active": true,
  "paused": false,
  "billing_mode": "prepaid",      // or "metered"
  "remaining_days": 11,           // null on metered
  "day_active": true,             // today counts as an active day
  "config": {
    "capture_mode": "full",       // or "errors_only"
    "sampling_rate": 1,           // 0..1
    "console": true, "network": true, "dom": true
  }
}

200 - not authorized

{ "authorized": false, "paused": true,  "reason": "paused", ... }
{ "authorized": false, "paused": false, "reason": "no_day_credits", ... }

401

{ "authorized": false, "error": "invalid_api_key" }

Billing semantics

The first authorized check of each UTC day marks it active. On prepaid, that consumes one day from the wallet. Paused projects never consume days.

API keys

Keys use the format rmp_ followed by 40 hex characters. A key is issued with each purchase and can also be generated in the portal. Keys are shown once and stored only as hashes.

Team API

Connect your platform's team management with the same project API key. Roles: admin, developer, viewer.

GET    /api/public/v1/team                        # member list
POST   /api/public/v1/team   {"email","role"}     # invite by email
PATCH  /api/public/v1/team   {"email","role"?,"status"?}  # change role / status
DELETE /api/public/v1/team?email=dev@company.com              # revoke access
DELETE /api/public/v1/team?email=dev@company.com&remove=true  # remove member

Roles and permissions

A key acts with its creator's current role. Owner and admin keys can read and manage the team; developer and viewer keys can only list members (writes return 403 forbidden). Keys created by a member stop working on the Team API once that member is revoked or removed. Members cannot change or remove themselves.

             owner/admin  developer  viewer
Team: list        ✓          ✓         ✓
Team: manage      ✓          –         –
Recording switch  ✓          ✓         –
Capture config    ✓          ✓         –
Billing, region   ✓          –         –
Create API keys   ✓          ✓         –
Revoke any key    ✓        own only    –

Outbound hooks

Invites, role changes and revocations - from the portal or the API - are POSTed to your configured hook URL as member.invited, member.role_changed, member.revoked and member.removed, signed with HMAC-SHA256 in X-Signature.