Replay Cases

Save Real Events as Repeatable Checks

Replay Cases turn a captured webhook or normalized email into a durable regression check owned by its endpoint. Each case keeps an encrypted source snapshot, a fixed target, and at least one deterministic assertion, so it remains runnable after the original event expires.

Deterministic Assertions

Every case requires an expected HTTP status, a type-strict JSON subset, or both. Status checks support exact codes and status classes. JSON checks recursively compare expected keys and values, with positional-prefix matching for arrays.

Immutable Run Evidence

Each run creates a new historical record containing bounded evidence for the outbound request, response, assertion result, timing, and usage. Runs are never overwritten, and ambiguous post-send failures are recorded as unknown instead of being retried automatically.

Web, API, and MCP

Create, edit, run, and inspect Replay Cases from the workspace UI, the endpoint-scoped REST API, or MCP. Cases can be saved directly from request and replay workflows.

Plan Limits

Downgrades preserve existing cases. Saving pauses only while an account remains above its new limit.