Your progress is only saved in this browser. to protect it and pick up on any device.

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.

Mission Trajectory
0 / 12·0%Pre-launch
  1. 1Launch
  2. 2Orbit
  3. 3Transit
  4. 4Flyby
  5. 5Return
  6. 6Splashdown
1

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.

  1. In your collection, open the health folder and select the Health Check request — its URL uses {{baseUrl}}.
  2. Click Send — expect a 200 OK response.

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.

  1. Open Register Crew Member (POST /register).
  2. Go to the Body tab and enter your details:
json
{
"name": "",
"email": ""
}
  1. Click Send — the response includes your callsign, API key, and sigil (SVG badge). You'll save the API key in the next step.
2

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

  1. Open the Register a new crew member request (POST /register) — stay on the response from the previous step if you still have it.
  2. 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
  3. Start a new chat so this task has a clean context.
  4. 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.
  5. Enter this prompt:

Generate an After response script that reads api_key from the response body and saves it to the environment variable apiKey

  1. Review and accept the script, then Save the request.
  2. 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.
  3. Open artemis.local — apiKey should now be populated in the local Value column.

Option B — Manual

  1. On the Register a new crew member response, copy the api_key value.
  2. Open artemis.local (it may already be open in a tab).
  3. Paste the key into the apiKey row's Value column — leave Shared Value empty.
  4. Click Save (Ctrl/Cmd+S).
Important: An API key is sensitive — keep it in the local Value column, never in Shared Value. For this module, local Value is enough. Best practice elsewhere is to store the secret in the Postman Vault, then reference that vault secret from the environment Value field.

Check it works: In the mission folder, open Get mission overview (GET /mission) → Send → expect 200 OK.

Troubleshooting 401 errors:

  • Verify apiKey has 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).

3

Build Mission Dashboard

  1. In the mission folder, open Get mission overview (GET /mission) — you may already be on it from the previous step.
  2. Open Agent Mode if it isn't already visible ( in the bottom-right, or universal search → > → Open Agent Mode).
  3. 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.
  4. 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.

  1. Review and accept the script, then Save the request — confirm it appears under Scripts → After response.
  2. Click Send again so the new After response script runs.
  3. In the response panel, open the Visualize tab to see your dashboard.
Tip: Results vary since LLM outputs differ. Tell Agent Mode what to fix — e.g. "Make the sigil bigger" or "Add a progress percentage." — then save and Send again.
4

Mission Log Blitz

Create three mission logs — category diversity drives mission progression, so each log uses a different category.

  1. Make sure artemis.local is selected in the environment selector (top right).
  2. In the mission folder, open Create a mission log (POST /logs).
  3. 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.

json
{
"title": "",
"description": "",
"phase": "",
"category": "",
"crew_member": ""
}

Log 2 of 3 — Life support

Replace the body with this, then Send again — expect 201 Created.

json
{
"title": "",
"description": "",
"phase": "",
"category": "",
"crew_member": ""
}

Log 3 of 3 — Communication

Replace the body with this, then Send again — expect 201 Created.

json
{
"title": "",
"description": "",
"phase": "",
"category": "",
"crew_member": ""
}

Allowed field values

FieldAllowed values
phasepre-launch, launch, transit, lunar-approach, orbit
categorynavigation, life-support, communication, science, anomaly, crew-status
crew_memberwiseman, glover, koch, hansen
Note: Logs with category 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.