This module stands on its own, so you'll rebuild the workspace and collection here — and have Agent Mode add a baseline of tests in one go, so the advanced work in later parts has a real suite to build on.
Create Your Workspace
Every testing project starts with a workspace to keep your collection, requests, and results organized. You'll create one by hand through Postman's UI — the same flow you'd use for any real project.
-
Open Postman (desktop app or web) and sign in.
-
Click Workspaces in the Postman header, then click Create.
-
On the Create your workspace form, name it exactly, replacing
[Your Name]with your own name:[Your Name] - API Testing Advanced -
For Who can access, open the dropdown and choose Only you and invited people — Internal is already selected.
-
Leave the template on Blank workspace (already selected), then click Create Workspace.
Build the Movies API Collection with Baseline Tests
Now bring in Agent Mode — Postman's AI assistant that completes tasks from natural-language prompts, like scaffolding requests and writing tests. Open it from the homepage query box (Let's go), or from the panel in the bottom-right corner of any workspace (switch to the AI tab).
A note on approvals: Agent Mode shows you what it's about to do and asks for confirmation before it changes anything — so you stay in control. If you've enabled Auto-run, it applies those actions without prompting. Either way, read what it proposes before you move on.
Rather than click through the request builder by hand, describe the whole API in plain English and let Agent Mode scaffold every request — and its baseline tests — for you. You'll also organize them under a Happy Path folder, so the negative tests you add later can sit in their own Unhappy Path folder and your suite cleanly separates what should work from what should fail. The Movies API has five endpoints:
| Method | Endpoint | Description |
|---|---|---|
| GET | /movies/animation | List all animated movies |
| GET | /movies/animation/:id | Get one movie |
| POST | /movies/animation | Create a movie |
| PUT | /movies/animation/:id | Update a movie |
| DELETE | /movies/animation/:id | Delete a movie |
A movie has an id (number), title (string), posterURL (string), and imdbId (string).
Make sure you're in your [Your Name] - API Testing Advanced workspace, then run a prompt like:
Create a collection called "Movies API" in this workspace. Inside it, create a folder named "Happy Path" and add a request for each of these endpoints: GET /movies/animation, GET /movies/animation/:id, POST /movies/animation, PUT /movies/animation/:id, DELETE /movies/animation/:id. Use https://api.sampleapis.com as the base URL, and set the id path variable to 1 on the by-id requests so their URLs are valid. For POST and PUT, include an example JSON body with id, title, posterURL, and imdbId. Then add baseline post-response tests: a status-code test on every request (GET expects 200, POST expects 201, PUT expects 200, DELETE expects 200 or 204), a Content-Type "application/json" test on the GET requests, and on GET /movies/animation a schema test that the body is an array whose items each have id, title, posterURL, and imdbId.
Review the requests and tests Agent Mode creates, then approve them — or, with Auto-run enabled, confirm the changes it applied.
See it for yourself: Send GET /movies/animation and open the Test Results tab in the response pane — the baseline status, Content-Type, and schema tests should all show green PASS results before you layer on the advanced checks.
A note on the practice API: GET requests return real data, but POST, PUT, and DELETE echo your input back without persisting it. That's a useful lesson in itself — you test what an endpoint promises, and part of testing is knowing what your API actually does. Where the sandbox differs from a production API, the steps below say so.