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.

0 of 1 steps0%

The UI push is great for a one-off publish. The Postman CLI runs the same sync from your terminal — useful when you already live in git, or when you later automate the step in CI.

1

Publish with `postman workspace push`

Run the CLI against your connected deskly-api folder so local Postman files sync to the same Cloud View you just used.

  1. Open the Postman terminal (or any terminal) in your connected deskly-api folder. Confirm you're still on the feature/ branch that has your collection.

  2. Confirm the Postman CLI is available:

    postman --version

    If the command isn't found, install the CLI, then retry. Pick one method:

    npm (Windows, macOS, and Linux):

    npm install -g postman-cli

    curl (macOS, Linux, and WSL):

    curl -o- "https://dl-cli.pstmn.io/install/unix.sh" | sh

    Don't mix both installers — you can end up with two postman binaries. More options: Install the Postman CLI.

  3. Log in to the Postman CLI. The command below uses the same API key already connected to LiftOff. The key stays masked on this page; Copy puts the real command on your clipboard so you can paste it into the terminal.

    command
    postman login --with-api-key $POSTMAN_API_KEY

    Connect your Postman API key in Settings first — then Copy will fill it into this command.

    Prefer a browser instead? Run postman login with no flags — a window opens and you sign in there.

    For CI/CD or a server with no browser, don't paste a personal key into the workflow. Store it as a secret named POSTMAN_API_KEY and run:

    postman login --with-api-key $POSTMAN_API_KEY

    Don't commit an API key to the repo.

  4. From the repo root (where .postman/ and postman/ live), publish:

    postman workspace push -y

    The -y / --yes flag skips interactive confirmation — handy in scripts. Omit it if you want to review the prompt first.

  5. Switch back to Cloud View in the desktop app and confirm Deskly API (and any other items you pushed) are still there.

Expected outcome: The CLI completes without errors, and Cloud View still shows your Deskly elements.

CI note (optional reading): The same postman workspace push -y command can run in GitHub Actions after merge — install the CLI, log in with a POSTMAN_API_KEY secret, then push. You don't need to add that workflow for this module; see Automate Native Git with CI/CD for the official example.

Caution: Keep secrets out of Git. Use local environment values in the app for credentials; only commit Shared values you intend to share.

Troubleshooting

  • Not logged in — Copy the masked command above (or re-run postman login for the browser flow). Use a POSTMAN_API_KEY secret only in CI or on a server with no browser.
  • Wrong directory — cd to the connected deskly-api root so the CLI can see .postman/ and postman/.
  • Nothing to push — Local View and Cloud View may already match; that's fine if Cloud View still shows Deskly API.