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.
Extend the API With One Prompt
In the CLI module, adding an operation meant editing the spec, adding a request, writing a test and linting. Describe that outcome once and let the agent do all four. Because your repo's skills say what "done" looks like, you only need to state the goal.
-
Send this prompt to your agent:
Add a `DELETE /tasks/{taskId}` operation to `openapi.yaml`. Give it an operationId, a description and a documented 404 response. Then add a matching "Delete task" request to the Tasks API collection with a `pm.test` that checks the status code, and run the spec lint and the collection lint.
-
Review the diff before accepting it. The spec change, the new
.request.yamlfile and the test should all be small and readable:git diffgit diff -
Commit and push, or ask the agent to:
Commit these changes with a clear message and push them.
Troubleshooting: If the agent adds the operation but no collection request, ask: "Also add the Delete task request to postman/collections/Tasks API." The request file must use the DELETE method and contain a pm.test( script.
Prompt a Failure Into the Mock
Happy-path mocks hide bugs. A client that has never seen a 404 won't handle one, so ask the agent to make the mock misbehave on purpose and prove your collection copes. The mock is code in your repo, so the change is a reviewable diff.
-
Send this prompt:
Update the Tasks mock in `postman/mocks/` so `GET /tasks/{taskId}` returns a 404 with the JSON body `{"error": "task not found"}` when the id is `missing`. Keep the existing behaviour for every other id. Then start the mock and run the Tasks API collection against it with the Local environment, and tell me what passed and failed.
-
Read the agent's report. Did it run the mock and the collection, and did it tell you what the 404 case did? If it only edited files, ask it to run them.
-
Commit and push the mock change:
Commit the mock change and push it.
Troubleshooting: LiftOff looks for a 404 and the text task not found in your mock files, so keep that exact wording in the body.