Guide

From Postman export to dashboard, in six steps

Everything below works the same on every tier - Plus and Pro just raise a few ceilings.

Import a collection

From Collections & Environments, tap Import collection. You can paste the raw JSON of a Postman v2.1 export, pick a .json file from storage, or just share it into Fathom from wherever it already is - Gmail, Drive, Slack. A .zip containing both the collection and its paired environment works too (Pro).

No collection handy? Describe one request

New request (no collection needed) lets you type a method, URL, headers, and a body directly - Fathom treats it as a one-request collection you can pulse-check right away.

Run a test

Open the collection, tap Run test, and pick Light, Medium, or Heavy (Plus) - each preset's concurrency and duration are computed from your actual phone's CPU, RAM, and network, so a preset never asks more of your device than it can safely give. Prefer exact numbers? Advanced mode (Plus) lets you set concurrent users, duration, and ramp-up yourself.

Read the result

Every run opens on a plain-language verdict - healthy, degraded, or failing - plus a one-line reason. Tap Show technical details (Plus) for latency percentiles, throughput and latency over time, and a breakdown of which endpoint is the weakest link.

Pin it to the Dashboard

From a collection's saved test templates, tap the pin icon and give it a name - "Login flow", "Balance check", whatever makes sense to you. The Dashboard shows every pinned flow's latest status as a single green or red dot.

Turn on auto-check (Pro)

Flip a pinned flow's switch on, pick how often (15 min up to 4 hours), and Fathom re-runs it quietly in the background - and posts a notification the moment one starts failing or degrading. Add the home-screen widget to see every pinned flow's status without even unlocking your phone.

A note on pre-request & test scripts

If your collection has a script that captures a login token and a later request that depends on it - Fathom runs both, in order, for real (Pro). A "Login" request's test script setting pm.environment.set('authToken', ...) makes {{authToken}} resolve correctly in every later request of that same run, exactly like it would in Postman itself.