Skip to content

Postman Import

Bring your Postman collection, keep plain YAML.

Turn a Postman collection into curl-runner YAML with one command or in the studio. You get a file per request and a .env. Secrets stay out of files.

Read the docsInstall curl-runner

Screenshots

  1. The Import dialog on the Postman collection tab with example-api.postman_collection.json picked: 5 requests in 2 folders. Two items need attention, a file to pick for the document field and the secret apiKey to set. The preview lists the five request files in customers and documents.
    See every file before you importPick a collection exported from Postman. The preview lists the request files you get and what needs your attention, before anything is written.
  2. The Import dialog after a Postman import: Imported 5 requests, and the variables are in .env. Needs your attention lists a file to pick for the document field, with an Open link, and the secret apiKey to set.
    Finish what the import leftThe summary lists what still needs you. Open goes straight to the request with a file to pick.

Plain YAML underneath

Each request becomes a file like this one. The CLI, CI and the studio run it as it is.

customers/list-customers.yaml
# Imported from Postman: Example API
# Lists customers, newest first.

request:
  name: List customers
  method: GET
  url: ${baseUrl}/v1/customers
  headers:
    X-Api-Key: ${apiKey}
  params:
    limit: "10"
    # starting_after: cus_1

Benefits

  • One file per request

    Each Postman folder becomes a folder and each request its own YAML file, so a change shows up as a small diff in a pull request.

  • Optional fields stay optional

    A header, param or form field you turned off in Postman comes in commented out. Uncomment it to switch it on.

  • Secrets stay out of files

    The CLI asks you to set secrets in .env.local, and the studio saves them to the macOS Keychain. Both list what still needs your attention.

Good for

  1. Moving a team off Postman
  2. Reviewing API changes in pull requests
  3. Running a shared collection in CI
  4. Regenerating YAML from a collection your build generates