RequestNest¶
Keep Postman. Skip the per-seat cost. Collaborate through git.
RequestNest lets a team share Postman collections and environments for free by using a git repo as the shared workspace — so you don't have to migrate to a different API client or pay for a Postman team plan.
Each teammate keeps their own free Postman account. RequestNest syncs each person's personal Postman workspace (via the Postman REST API) with a shared git repo — git is the source of truth, and secrets never land in it.
shared git repo <-> your personal Postman workspace
Why it exists¶
As of March 2026, Postman's free plan is single-user with no shared workspaces, and team collaboration runs $23/user/month (monthly; $19 annual). Postman's own native git sync requires a paid team workspace — it doesn't work with the personal workspaces free users have. The alternative is migrating to a git-native client (Bruno, Apidog, Requestly), which means leaving Postman behind.
RequestNest is for teams that want to stay on Postman: publish your collections to git, let teammates import them into their own workspaces — no migration, no paid seats — and it sanitizes secrets automatically so tokens never reach the repo.
See the Market analysis for the full picture.
Install¶
pip install requestnest # or: pipx install requestnest
requestnest --version
You'll need a Postman API key (Postman → Settings → API keys). Provide it when
init/setup prompts, or set REQUESTNEST_API_KEY.
Quickstart¶
Publisher — share collections you built in Postman:
requestnest init # pick which collections/environments to track
requestnest push # sanitize secrets, write JSON, commit & push
Consumer — use collections a teammate shared:
requestnest setup # import into your workspace + prompt for secrets
Day to day: pull to receive, edit in Postman, diff to preview, push to
share. Git is handled for you.
Learn more¶
- Project brief — design and architecture
- Manual test checklist — hands-on walkthrough
- Publishing — releasing to PyPI
- Source on GitHub