Connect a Postman API key to check your work
You do each step in Postman, then LiftOff uses your key to look at your workspace and confirm it's done. Connect once and it works for every module. Your key is saved in this browser and is only used to check your work in Postman.
- 1Launch
- 2Orbit
- 3Transit
- 4Flyby
- 5Return
- 6Splashdown
Health Check & Registration
Confirm the Artemis API is up, then register as crew. Make sure artemis.local is selected in the environment selector (top right) so {{baseUrl}} resolves from the environment you set up.
- In your collection, open the health folder and select the Health Check request — its URL uses
{{baseUrl}}. - Click Send — expect a
200 OKresponse.
Watch your mission progress on the launch graphic above, or open the step counter in the bottom-right corner for a closer look as you move through the steps.
- Open Register Crew Member (
POST /register). - Go to the Body tab and enter your details:
- Click Send — the response includes your callsign, API key, and sigil (SVG badge). You'll save the API key in the next step.
Auto-Save API Key with Agent Mode
Save the API key from registration into your artemis.local environment — with Agent Mode, or by hand.
Option A — Agent Mode
- Open the Register a new crew member request (
POST /register) — stay on the response from the previous step if you still have it. - Open Agent Mode if it isn't already visible. Use either path:
- Click the button in the bottom-right of the sidebar (expand the panel if it's collapsed), or
- Click the universal search bar at the top, type
>, then choose Open Agent Mode
- Start a new chat so this task has a clean context.
- Give Agent Mode the request as context: type
@in the prompt box and select Register a new crew member, or drag the request from the sidebar into the chat. - Enter this prompt:
Generate an After response script that reads
api_keyfrom the response body and saves it to the environment variableapiKey
- Review and accept the script, then Save the request.
- Click Send again on Register a new crew member. The first send (in the previous step) ran before this script existed — only a new send runs the After response script and writes
apiKey. - Open artemis.local —
apiKeyshould now be populated in the local Value column.
Option B — Manual
- On the Register a new crew member response, copy the
api_keyvalue. - Open artemis.local (it may already be open in a tab).
- Paste the key into the
apiKeyrow's Value column — leave Shared Value empty. - Click Save (Ctrl/Cmd+S).
Check it works: In the mission folder, open Get mission overview (GET /mission) → Send → expect 200 OK.
Troubleshooting 401 errors:
- Verify
apiKeyhas a value in artemis.local (Value column) - Confirm the request header uses
x-api-key: {{apiKey}} - Make sure artemis.local is selected in the top-right environment dropdown
After you validate, confirm your Artemis API key in the field below (paste apiKey from artemis.local).
Build Mission Dashboard
- In the mission folder, open Get mission overview (
GET /mission) — you may already be on it from the previous step. - Open Agent Mode if it isn't already visible ( in the bottom-right, or universal search →
>→ Open Agent Mode). - Start a new chat, then give Agent Mode the request as context: type
@and select Get mission overview, or drag the request into the chat. - Enter this prompt:
On the Get mission overview request, add an After response script that creates a card-style visualisation with
pm.visualizer.set. Render the SVG as HTML rather than an image. Keep all the fields in the card. Make it like a mission dashboard.
- Review and accept the script, then Save the request — confirm it appears under Scripts → After response.
- Click Send again so the new After response script runs.
- In the response panel, open the Visualize tab to see your dashboard.
Mission Log Blitz
Create three mission logs — category diversity drives mission progression, so each log uses a different category.
- Make sure artemis.local is selected in the environment selector (top right).
- In the mission folder, open Create a mission log (
POST /logs). - Open the Body tab. You'll send this request three times with different bodies.
Log 1 of 3 — Navigation
Paste this body, then Send — expect 201 Created. Note the log.id in the response; you'll need a log ID later.
Log 2 of 3 — Life support
Replace the body with this, then Send again — expect 201 Created.
Log 3 of 3 — Communication
Replace the body with this, then Send again — expect 201 Created.
Allowed field values
| Field | Allowed values |
|---|---|
phase | pre-launch, launch, transit, lunar-approach, orbit |
category | navigation, life-support, communication, science, anomaly, crew-status |
crew_member | wiseman, glover, koch, hansen |
anomaly cannot be deleted — only updated. Avoid anomaly for logs you plan to delete later.To validate: Open artemis.local, find apiKey in the Value column, click the eye icon to show the value if it is hidden, then copy and paste it below. This is a training API key — used once per browser session to validate later steps too, not stored on the server.