Session Sandbox Activity & Quota Status
Comprehensive overview of your personal identity token, sandbox mutation usage, rate limit status, and resource quotas.
Resource Quotas & Mutations
| Resource | Created (Quota) | Updated | Deleted | Usage |
|---|---|---|---|---|
| /Users | 0 / 30 | 0 | 0 | |
| /Posts | 0 / 30 | 0 | 0 | |
| /Comments | 0 / 30 | 0 | 0 | |
| /Todos | 0 / 30 | 0 | 0 | |
| /Custom | 0 / 30 | 0 | 0 |
How Session Sandboxing Works
Stateful mock API testing without account registration or logins
Automatic HMAC Identity Issuance
On your very first request, the server generates a cryptographically signed HMAC-SHA256 identity token issued via an HTTP-only cookie (pg_identity) or X-Playground-Identity header. No sign-up or API key is required.
Session Overlay Mutations
When you issue POST, PUT, PATCH, or DELETE requests, your mutations are recorded into a private session sandbox (overlay_records). Shared global seed data remains untouched for all other developers.
Virtual Merging Engine
Subsequent GET requests run through our Virtual Merging Engine. Your newly created records appear at the top, updates overlay in-place, and deleted items are filtered out specifically for your active session.