Live Traffic
Every request your app sends through FlowMock shows up here in real time — method, path, status, timing, full bodies — for you and for everyone else testing right now.
"It works on my machine."
"Send me a screenshot."
"The screenshot doesn't show the response body."
Traffic shows the response body. And the request body. And who sent it, from which device, three days ago.
Rows stream in with session avatars. One is pre-marked mocked.
Open Traffic and the feed is already live for every session on the environment. Most tools make you configure an identity before they'll show you a single request. FlowMock is observability-first: watch first, claim yourself later, and only when you want mocks to apply to you.
In-product visual
Every row carries a session avatar and a device hint — desktop, mobile, browser. Hover for the name. Filter to one teammate, or to five. The filters live in the URL, so pasting the link into Slack sends someone to exactly the view you were looking at.
In-product visual
Open a row, edit the response inline — JSON editor or a field-by-field form view if you'd rather not touch braces — and save it as a mock. Or describe the change in plain English and let the AI edit do it: "make all items expired", "return an empty list". One-click presets for Make empty and Return 500 are right there, and your recent edits are saved so you can rerun them on the next payload.
In-product visual
Collapse identical requests into one row with a ×100 counter. Filter by status bucket, search by path, flip to timeline view, pause the tail while you read. Logs are kept for 14 days, so yesterday's bug report is still reproducible today.
In-product visual
| Retention | 14 days |
|---|---|
| Captured | Method, path, query, request body, response body, headers, status, latency, device, session |
| Views | Table or timeline · JSON or form · live or paused |
| Filters | Session, path search, status bucket, errors-only, mocked-only, transformed-only |
| Traces | Applied mock and transform ids, plus which rule fired and any expression errors |
| Sharing | Filter state and log id are both in the URL |
Common objection
You decide what's stored, per field. Endpoints has a redaction tab: name a field, pick request or response body, mark it Redacted, and it's dropped at capture time — never written. Set the project default to store nothing and opt fields in, or store everything and opt sensitive fields out. Redaction applies to intercepted traffic only; mocks you write yourself are always stored as typed.
Free plan, no card, two-minute setup.