Browser extension

Click a request. Mock it. No code change.

The FlowMock extension routes your browser's API calls through FlowMock and adds a FlowMock tab next to Network in DevTools. Pick any request, change what comes back, reload. Only your session sees it.

"Can we try FlowMock on the staging app?"

"Someone has to change the API URL and redeploy first."

"So… next sprint?"

Or: install the extension, open DevTools on the staging app you already use, and mock the first request before the coffee is done.

DevTools → FlowMock

The page's API requests, labelled with what FlowMock did to each.

  • Click a row → Response / Request / Headers
  • Mock → edit the status or body → Mock it for my session
  • Active lists everything on for you, with Turn all off

No code change, no deploy, no config PR.

Turn FlowMock on for a site and the extension sends that site's API calls through your FlowMock environment. Your app keeps its real API URL. Teammates without the extension keep hitting staging as before, so you can try FlowMock on the app you test today.

In-product visual

It finds the right environment by itself.

FlowMock watches where the site's requests go and picks the environment whose API they call. Each site keeps its own environment, so staging, a preview deploy, and localhost can each point somewhere different. A site you never turned on is never touched.

In-product visual

Mock from the request you're looking at.

Every API request the page makes is listed with its status, timing, and a label: Mocked, Transformed, Delayed, or Proxied. Click Mock and the editor opens with the real response filled in. Change the status, the JSON, or add a delay, and it's on for your session.

In-product visual

See what's on. Turn it all off.

The Active view lists the running scenario and every mock and transform on for you, with how often each fired in the last ten minutes. Switch anything off from its row, clear everything at once, or turn on a mock or scenario from the team's library.

In-product visual

Impossible to forget a mock is on.

After a mocked response the page glows for ten minutes — or shows a side line, a ribbon, or a pill, your choice — and the toolbar badge counts the responses FlowMock changed on that tab. No more "why is checkout broken for me?"

In-product visual

Your credentials stay where they belong.

The extension gets its own revocable credential, never your password or an org API key, and pages you test never see it. Apps that sign in with cookies stay signed in through FlowMock. Revoke any browser from your account settings.

In-product visual

Details a careful buyer checks

BrowsersChrome and Firefox, desktop
Where it livesA FlowMock tab in DevTools, plus a small button on pages you turned on
ScopeOnly sites on your Sites list, each bound to one environment
Mocks you createDrafts on your own session, editable in the dashboard
RemindersPage glow, side line, ribbon, or pill · toolbar badge count
PriceFree forever for one person, on every plan

Common objection

“We'll still need the proxy URL for CI and mobile.”

Yes, and nothing changes when you get there. The extension and the proxy URL use the same environments, mocks, scenarios, and transforms. Start in the browser today, point CI and the mobile build at the proxy URL when you're ready, and everything the team built keeps working.

One URL change. That's the whole integration.

Free plan, no card, two-minute setup.