Running the service means your requests return real responses as you build them. Deskly is a small Node.js/Express app, so you need Node.js 18 or newer installed. It keeps its data in memory and resets on restart.

1. Open the Postman terminal at the bottom of the desktop app to run the CLI commands. If it doesn't already open in your deskly-api folder, change into it:

   Copy

   cd deskly-api

2. Confirm Node.js is installed:

   Copy

   node --version

3. Install the dependencies and start the server:

   Copy

   npm install
   npm start

4. The console prints the base URL and the API key it's using:

   Copy

   ▸ Listening  http://localhost:4000
   ▸ API key    demo-key

5. Confirm it's up from Postman. Open a new HTTP request tab (click the + in the tab bar), then paste the health check curl command into the URL field — Postman parses the curl into a request automatically:

   Copy

   curl http://localhost:4000/health

   Hit Send. You should get a 200 with {"status":"ok","service":"deskly", ...}, confirming the server is up and running. The /health endpoint is public, so no API key is needed.

   Switch back to the terminal running the server and you'll see it log the request — the timestamp and response time will differ each time:

   Copy

   2026-08-13T17:26:28.465Z  INFO  GET    /health 200 3.9ms

Note: Every endpoint except /health requires the header X-API-Key: demo-key. Leave the server running while you build your requests in the next step.

You've already sent the Health Check request by hand — the "hello world" that proves you can drive the API. Rather than hand-crafting the rest one curl at a time, you'll let Agent Mode read the Deskly source code sitting right next to your collection and build the remaining requests for you. That's the payoff of Native Git: the service code and your Postman elements share one folder, so the agent can scan the routes directly. You stay in Local View, so everything the agent creates is written straight into the Collection V3 YAML under postman/collections/.

1. Confirm you are in Local View (control in the bottom left), then select Local Items in the left sidebar so the Collections list is in view. In Local View, Postman shows the name of the branch you're currently on — for this service it reads main. Click + → Collection and name it:

   Copy

   Deskly API

2. You already created the Health Check request in the previous step — no need to recreate it. With that request tab active, click Save, name it Health Check, and save it into the Deskly API collection.

   Because you're in Local View, saving writes these straight to disk. Open the Files tree and you'll see Native Git created postman/collections/Deskly API/, with your request stored as its own file, Health Check.request.yaml. Every element you save — collections, requests, and so on — is written as an individual YAML file under postman/, which is exactly what makes them reviewable in a pull request.

3. Open Agent Mode. Toggle open the right sidebar using the control in the bottom-right corner, or open the universal search and type > followed by agent mode to surface the option to open it.

4. Give the agent its context. Type @ and select your Deskly API collection so it writes into the right place, then point it at the Deskly service's source files — the Express routes in your connected folder are what it scans for endpoints.

5. Send a prompt like this (adapt the wording if you like):

   Copy prompt

   Agent Mode Prompt: Scan the Deskly API source code in this connected repo for every HTTP endpoint. For each one that isn't already in my "Deskly API" collection, add a request that targets http://localhost:4000, includes the X-API-Key: demo-key header, and has an example JSON body where the route expects one. Don't recreate the Health Check request I already saved.

6. Unless you've turned on Auto-run, Agent Mode asks for confirmation before it changes anything — review the endpoints it found and approve the actions (with Auto-run enabled it applies them without prompting). When it finishes, expand the Deskly API collection and confirm the new requests are there.

7. Spot-check the agent's work: open one of the generated requests (for example Create Booking) and hit Send against your running server. The agent reads the code, but you still verify the request returns what you expect.

Expected outcome: the Deskly API collection holds the endpoints the agent discovered from the source alongside your Health Check request, and Postman has written a collection file under postman/collections/ in your repo. Because the agent reads the routes directly from the source, it may create more requests than the table below — and it chooses its own names, so you'll likely see labels like Get All Desks or Delete Booking rather than the exact ones here. That's expected; the table lists the core endpoints to check against, not a strict count. Deskly exposes these:

Request	Method & path	Notes
Health Check	GET /health	You saved this by hand; public, no key
List Desks	GET /desks	Needs X-API-Key: demo-key
Get Desk	GET /desks/desk-1	Needs X-API-Key: demo-key
List Bookings	GET /bookings	Needs X-API-Key: demo-key
Create Booking	POST /bookings	Returns 201; use today's date or later (YYYY-MM-DD). Reusing desk-1 on a booked date returns the 409 conflict
Get Booking	GET /bookings/bkg_seed01	Needs X-API-Key: demo-key; booking IDs look like bkg_…, and bkg_seed01 is seeded on startup
Delete Booking	DELETE /bookings/bkg_seed01	Needs X-API-Key: demo-key; returns 200 with released: true

Troubleshooting: If the agent misses the API key, open the request and add the X-API-Key: demo-key header, or re-prompt it to "add the X-API-Key: demo-key header to every request except Health Check." A 401 (MISSING_API_KEY) or 403 (INVALID_API_KEY) means that header didn't come through; a connection error means the server from the previous step isn't running on port 4000. Prefer to build the requests by hand? Open a new HTTP request tab, paste a curl into the URL field so Postman builds it, then save — for example curl http://localhost:4000/desks -H "X-API-Key: demo-key". The full endpoint list is in the table above.