How to Record Postman
Record Postman without exposing API keys and secrets. Guide for API documentation, test script tutorials, and integration demo recordings.
When you’d need to record Postman
API documentation and onboarding
Record walkthroughs of your API — show each endpoint, example requests, expected responses. New developers consuming your API watch the recording instead of reading 50 pages of docs.
API testing workflow tutorials
Record how to write test scripts, use pre-request scripts, chain requests with variables, and run collection tests. Postman's testing features are powerful but poorly understood — video shows the full workflow.
Bug reproduction with API context
Record the exact API request that triggers a bug — headers, body, response. Attach the recording to the bug report. Backend developers see the full HTTP context without asking 'can you send me the curl?'
Integration demos for partners
Record your API integration flow for external partners. Show authentication, key endpoints, and expected data formats. Partners follow along instead of deciphering your API docs.
Recommended settings
Things to know
- •Postman's environment variables may contain API keys, tokens, and secrets — the Environment quick-look panel exposes all values
- •Request history in the sidebar shows every API endpoint you've called, including internal/staging URLs
- •Response bodies can contain user PII, database records, or internal system data
- •Postman's collection sidebar shows all saved requests — collection and folder names may reveal internal API structure
Step-by-step
- 1
In Screenify Studio, select Window Capture and pick the Postman window.
Record at 1440p — response JSON bodies and request headers are dense monospace text that needs resolution.
- 2
Open Postman. Before recording, check your Environment variables: click the eye icon (top right) to see current environment values. API keys, tokens, and secrets are displayed in plain text. Switch to a demo environment with non-sensitive test keys, or close the quick-look panel.
- 3
Review the request history (bottom panel or sidebar). Every endpoint you've called is logged: 'POST https://internal-staging.company.com/api/users/delete'. Clear history if it contains sensitive internal URLs.
- 4
Create a clean collection for the recording. Don't record in your personal workspace with 200 saved requests — create a new collection (Cmd+N > Collection) with only the requests you'll demonstrate.
- 5
Start recording. When sending a request (Cmd+Enter), wait for the response to fully load before explaining it. Scroll through the response body slowly — JSON responses can be 100+ lines, and rapid scrolling is unreadable.
For test scripts and collection runner
- 6
For test script tutorials, click the 'Tests' tab on a request. Write test assertions (pm.test, pm.expect) and explain each line before running. After running (Send), show the Test Results tab to demonstrate pass/fail output.
- 7
For collection runner demos, click 'Runner' in the sidebar. Configure iterations, data files, and delay. Run the collection and show the results summary — this demonstrates batch API testing.
- 8
When demonstrating pre-request scripts and variable chaining, show the flow: Request 1 extracts a token → saves to variable → Request 2 uses the variable in headers. Run them sequentially and show the variable updating in real-time.
Pro tips
Auto-zoom on response JSON. API responses are rendered in 12px monospace. A JSON body with nested objects, arrays, and 50+ fields is unreadable at normal zoom. When you click on a specific field to explain it, auto-zoom zooms in so viewers can read the actual values.
Use a demo environment, never production. Postman environments store API keys, tokens, and base URLs as variables. Your production environment has real secrets. Create a 'Demo' environment with test API keys or mock values. Switch to it before recording: environment dropdown (top right).
Keyboard overlay for Cmd+Enter. The most common action in Postman is sending a request. Cmd+Enter is the shortcut. Without overlay, viewers see a response magically appear and don't know you pressed Send. With overlay, they learn the shortcut.
Clean response bodies of PII. If your API returns user data (names, emails, addresses), the response body in your recording contains that PII. Use mock data, test accounts, or a staging environment with sanitized data.
Common mistakes
Exposing API keys in environment variables. You click the environment quick-look icon and your production API key, JWT secret, and database connection string are on screen. Use a demo environment with test keys. Never record with production environment selected.
Recording with real user data in responses. You send a GET /users request and the response contains 'John Smith, john.smith@company.com, 555-0123'. Use test data or a staging environment. Real PII in tutorial recordings is a compliance violation.
Scrolling through 200-line JSON responses at full speed. Viewers see green and white lines blur past. Collapse unnecessary JSON sections (click the arrow to collapse objects), or copy the relevant section and paste it in a new tab for focused explanation.
Not showing the full request before sending. You click Send immediately. Viewers never see the URL, method, headers, or body before the response appears. Show the request tab by tab (Params, Headers, Body), explain the setup, THEN send.
Related guides
Record Postman with Screenify Studio
AI auto-zoom on clicks, instant captions in 50+ languages, cursor highlighting, and studio-grade export. Free plan, no watermark.
Try Screenify Free
