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
Update a Mission Log
Update one of the logs you created earlier so the mission records a change.
- Make sure artemis.local is selected in the environment selector (top right).
- In the logs folder, open List mission logs (
GET /logs) and click Send. - Pick a log
idfrom the response (or use anidyou noted when you created a log). - In the logs folder, open the {id} sub-folder, then open Update a mission log (
PATCH /logs/:id). - Replace
:idin the URL with the log ID you chose. - Open the Body tab and set:
- Click Send — expect
200 OK.
To validate: If you already pasted your Artemis training API key on an earlier step, LiftOff reuses it for this check. Otherwise paste it from artemis.local → apiKey (Value). Session only — not stored on the server.
Delete a Mission Log
Delete one non-anomaly log so the mission records a removal.
- Make sure artemis.local is selected in the environment selector (top right).
- If you need an ID, open List mission logs (
GET /logs) in the logs folder and Send. - Pick a non-anomaly log
idfrom the response. - In the logs folder, open the {id} sub-folder, then open Delete a Mission Log (
DELETE /logs/:id). - Replace
:idin the URL with that log ID. - Click Send — expect
200 OK. - Enter the deleted log ID below and validate.
Caution: Logs with category anomaly cannot be deleted — only updated. Choose a non-anomaly log.
To validate: Enter the deleted log ID below. Your Artemis training API key is reused from this browser session if you already entered it — otherwise paste it from artemis.local → apiKey (Value). Session only — not stored on the server.
Request Mission Briefing
Request a briefing that summarizes your mission status, log counts by category, and what to do next.
- Make sure artemis.local is selected in the environment selector (top right).
- In the mission folder, open the brief sub-folder, then open Generate a mission briefing (
POST /mission/brief). - Open the Body tab and set:
- Click Send — you'll receive a briefing with status, category counts, and recommendations.
To validate: If you already pasted your Artemis training API key on an earlier step, LiftOff reuses it for this check. Otherwise paste it from artemis.local → apiKey (Value). Session only — not stored on the server.
Verify Splashdown
Confirm the mission is complete — splashdown means completion_percentage is 100.
- Make sure artemis.local is selected in the environment selector (top right).
- In the mission folder, open Get mission overview (
GET /mission) and click Send. - Check for splashdown in either place:
- Visualize tab — use the mission dashboard you built earlier and look for
100%completion - Response JSON —
completion_percentage: 100and all steps showingcompleted: true
- Visualize tab — use the mission dashboard you built earlier and look for
If you see 100% — congratulations, you've achieved splashdown!
If not 100%, check which step is incomplete. You likely need more logs across different categories. Run Generate a mission briefing (POST /mission/brief in mission → brief) for recommendations — it tells you exactly what's missing.
| # | Requirement | Request |
|---|---|---|
| 1 | 3+ logs created | Create a mission log |
| 2 | Update at least one log | Update a Mission Log |
| 3 | Delete a log | Delete a Mission Log |
| 4 | Get a mission briefing | Generate a mission briefing |
| 5 | Verify splashdown | Get mission overview |
To validate: If you already pasted your Artemis training API key on an earlier step, LiftOff reuses it for this check. Otherwise paste it from artemis.local → apiKey (Value). Session only — not stored on the server.