Skip to content
korAPI

Moving from Postman

  1. In Postman, export the collection as Collection v2.1, and export each environment (and your globals, if you use them).
  2. In korAPI choose Import… (⇧⌘I (Ctrl+Shift+I)) and select all the files at once.
  3. Choose where the new collection folder goes.

korAPI keeps your folders and the order of your requests. Globals become collection variables, and each environment becomes an environment. Values that are marked secret, or look like one (password, token, api_key…), go to your system keychain instead of the files.

Scripts

Section titled “Scripts”

Pre-request scripts become Before request and tests become After response. Scripts that use pm. run as they are, with the same Chai expect and CryptoJS. A few Postman features do not exist in korAPI; the import report lists every script that uses one.

The import report

Section titled “The import report”

Every import ends with a report of anything that needs a look: :path variables that had no value, OAuth settings without their tokens (sign in again), file fields to choose again, and unsupported script features. Copy Report puts it on the clipboard.

What is different

Section titled “What is different”
  • Environment values win over collection variables, as in Postman.
  • A URL typed without http:// or https:// gets https://.
  • Environments marked as production are locked until you unlock them, and load tests never run against them.