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.
Create the Mission Repo and Workspace
In this module you never open the Postman app. Your mission lives in a local git folder and a coding agent with the Postman plugin does the work: you describe what you want, and the plugin decides which skills and tools to use. The cloud workspace is a mirror of that folder, and a small binding file ties the two together. LiftOff validates the cloud workspace, so at each checkpoint your prompt asks the agent to publish what you built locally.
- Create the folder and make it a git repo:
mkdir artemis-mission-control-agent && cd artemis-mission-control-agentmkdir artemis-mission-control-agent && cd artemis-mission-control-agentgit initgit initcurl -fsSL -o openapi.yaml https://raw.githubusercontent.com/mishra-aanchal/artemis-mission-control-api-workshop/refs/heads/main/openapi.yamlcurl -fsSL -o openapi.yaml https://raw.githubusercontent.com/mishra-aanchal/artemis-mission-control-api-workshop/refs/heads/main/openapi.yamlThe Postman CLI needs an origin remote to bind a workspace, and it names the workspace after it. The [your username] part is filled in from your Postman profile once your API key is connected, and you can edit it (any name works). The remote is only a placeholder: nothing is ever pushed to it. The curl command saves the Artemis OpenAPI spec as openapi.yaml at the repo root, so Postman finds it when it sets up the workspace.
- Start your coding agent from the repo root. If you have not installed the Postman plugin yet, run
npx @postman/postman-plugin@latest installfirst (it installs into every supported agent it finds, including Claude Code, Cursor and Codex).
claudeclaudeSwap claude for the command that starts your agent.
- Send this prompt:
Expect: a workspace named your-username/artemis-mission-control-agent (the Postman CLI names it after your origin remote) in your Postman account, and a workspace id in .postman/resources.yaml. Nothing needs publishing yet.
Troubleshooting:
- Not logged in → run
postman login, then retry. - The agent says a workspace is already recorded for this repo → ask it to replace the old binding in
.postman/resources.yaml. - Validation says no workspace found → the workspace name must end with
/artemis-mission-control-agent, which means theoriginURL must end with that repository name. Ask your agent to list your workspaces and to showgit remote -vto check.
Generate the Collection from the OpenAPI Spec
The Artemis API is described by an OpenAPI spec, and a spec is enough to generate a full collection. The spec is already in your repo as openapi.yaml: you will have your agent generate the collection locally from it, then publish it to your workspace.
- In your agent, send this prompt:
- Review what it created. The collection is a folder of v3 YAML files under
postman/collections/Artemis Mission Control/, withmissionandlogsfolders and requests such as Health check, Register a new crew member, Get mission overview and Create a mission log.
Expect: the agent reports the new collection and the Artemis spec in your workspace, with the collection linked to the spec. LiftOff looks for a collection whose name contains Artemis and Mission.
Troubleshooting: If validation says no collection was found, the publish has not happened yet. Ask your agent to publish your work to your workspace and validate again.
Create an Environment
An environment holds variables you reuse across requests, so one collection can run against different targets. It is just a YAML file in your repo, postman/environments/artemis.local.environment.yaml, which makes it easy for an agent to create and review.
- Send this prompt to your agent:
- Check that
postman/environments/artemis.local.environment.yamllistsbaseUrl,apiKeyandlogId.
Expect: the agent reports the new environment artemis.local with its three variables.
Set the Base URL and Plan for the API Key
LiftOff reads your pushed environment through the Postman API, so baseUrl must be set in the file and pushed. The apiKey is different: it is a credential, so it never goes into a committed file or into the cloud environment as a plain value. You leave it empty here and decide in Part 2 where it lives.
- Send this prompt to your agent:
- Open
postman/environments/artemis.local.environment.yamland check that onlybaseUrlhas a value.
Where the API key will live. You get the key when you register in the next part. There are two ways to keep it out of your files:
| Path | Who it is for | How it works |
|---|---|---|
| Vault | Postman Solo, Team and Enterprise plans | The key is stored in your team's Shared Vault with the Postman CLI. Your environment file only holds a reference to it. |
| Env var | Free plans (Shared Vault is not available) | The key stays in a shell variable, ARTEMIS_API_KEY, that you pass to commands. The environment's apiKey stays empty. |
Not sure which one you have? Try the Vault path in the next part. If creating the secret is refused, switch to the Env-var path.
Troubleshooting:
- Validation says
baseUrlis empty → the environment has not been published yet. Ask your agent to publish it, wait a few seconds and validate again. - Validation says the URL is wrong → it must be exactly
https://artemis.up.railway.app.