Stateful CRUD API
Test create, read, update, and delete workflows with temporary state.
Checking this session…
Start with useful test data
Records become a real API. Keep the seed to restore a known starting point.
Up to 200 records and 64 KiB of seed JSON. Each record can contain 40 fields and 4 KiB. IDs are strings; omitted seed IDs are assigned deterministically. Live changes are isolated to this API and expire with it.
Import a CRUD configuration
Import updates this editor only. Apply it explicitly to create an endpoint or replace its live records. Exports contain seed data, not credentials or the current live collection.
Open an existing mock API
About Stateful CRUD API
Create a real stateful test API with seeded records, list/search/sort/pagination, record creation, replacement, patching and deletion.
When to use it
Create a real stateful test API with seeded records, list/search/sort/pagination, record creation, replacement, patching and deletion.
POST /items → GET /items/:id → PATCH /items/:id → DELETE /items/:idHow to use it
- Configure the endpoint and choose private or public access.
- Create it and send requests from your client.
- Inspect test output, update or delete the resource when finished.
A mock that remembers changes
Start a collection from a JSON seed, then use real GET, POST, PUT, PATCH and DELETE requests. New records appear in subsequent reads. The workbench shows live records in a searchable, sortable table with pagination; inspect a row to edit its formatted JSON. Nested fields remain structured JSON rather than being flattened into misleading text.
The seed and live records are separate. Reset restores the seed after confirmation, while applying a new configuration replaces it and resets the collection. Export configuration keeps the seed; Export live records snapshots the current data. Neither export includes sharing credentials.
Sharing and lifecycle are part of the tool
New resources are private. Callers supply a separate X-Access-Token header or authorized workspace access; management tokens control configuration and reset. Public sharing permits anyone who knows the endpoint to read and change records. Use synthetic test data. Each resource has its own records, expiry and storage allowance, and deletion removes its live state.
Writes are serialized and checked against storage limits. Responses expose X-Mock-Revision; send X-Mock-If-Revision to reject a write based on an outdated collection with HTTP 409. The workbench uses this check and refreshes after conflicts instead of silently overwriting another caller’s changes.
Test a complete integration
Use in API scenarios prepares five requests: create a test record, read it, update its status, delete it, and verify the missing record. The draft contains a secret placeholder for private sharing; enter the access token separately. Opening a draft never runs it. Review the requests before sending them.
This is one bounded collection per resource: 200 live records, 4 KiB per record and 128 KiB of live JSON. It is a temporary test API, with no relational queries, custom server code or production database guarantees. Hosted scenario execution requires a publicly reachable origin; local Docker endpoints can be tested directly with curl, SDK, CLI, SSH or MCP.
Limits & privacy
Uses an expiring mock resource, private by default, with separate management and access credentials. Public access is optional. Standard resource quotas, ownership, renewal and deletion apply. Private access tokens are sent in headers, never in share URLs. One collection per mock. Up to 200 live records, 4 KiB per record and 128 KiB of live JSON; seed data up to 64 KiB. Updates are atomic in memory and PostgreSQL. X-Mock-Revision and optional X-Mock-If-Revision prevent stale writes. Reset restores the configured seed and requires management access. Updating configuration resets live records. Ordinary mock resource storage, retention and rate limits apply. Public sharing allows others to modify the collection; private is the default. No SQL or user code executes.
Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.