Jasper + Postman: bring your collections across and keep them in step

Connect your Postman API key and Jasper copies the collections and environments in the workspaces you pick into its API client, then keeps checking Postman for changes. Sync is one way: Jasper never changes anything in Postman.

Available All plans, including the free plan
Connect Postman Read the setup guide

What you can do

  • Move a team off Postman gradually: keep editing in Postman while everyone starts using Jasper.
  • Give everyone in the agency the same client API collections, while each person keeps their own environments and credentials.
  • Keep credentials out of shared collections: values that look like secrets move into each person's private, encrypted environment.
  • Run synced collections in Jasper's API client, or on a schedule with monitors.

What syncs

Data Direction When
Collections, folders and requests in the workspaces you pick Postman → Jasper When you save the workspaces to sync, then every 15 to 240 minutes. Sync now checks at once.
Environments and their variables Postman → Jasper On the same schedule. They stay private to you.
Values that look like secrets Postman → Jasper Moved into your own encrypted "Postman secrets: <collection name>" environment, one per collection. Teammates see the variable and add their own value.
Your changes in Jasper Not synced Nothing is sent to Postman. Your edits are kept when Postman changes other fields.

Set up in 4 steps

Who can do this: Anyone in your organisation, with their own Postman API key.

  1. In Postman, create an API key. It starts with PMAK-.
  2. In Jasper, open Personal settings, then Integrations, paste the key into the Postman card and click Connect.
  3. Tick the Postman workspaces to sync and click Save.
  4. Jasper copies your collections and environments. Click Sync now whenever you want it to check Postman straight away.

Permissions we ask for, and why

A Postman API key carries your own Postman access. Jasper only reads with it, and sends it only to Postman.

Permission Why Jasper needs it
Postman API key (PMAK-) Read your Postman name and team, the workspaces, collections and environments the key can see, and the key's monthly API quota.

Your data

  • Your Postman API key is stored encrypted and is never written to logs or error messages.
  • Synced collections are shared with everyone in your Jasper organisation. Environments stay private to you.
  • Secret values are encrypted, and the shared copy of a collection holds a placeholder instead of the value.
  • Before a sync changes a collection, Jasper saves a version, so you can undo it from the version history.
  • Disconnecting deletes the key. Your synced collections and environments stay in Jasper.

Our privacy policy covers what we store, where, and for how long.

Limits and what is not synced

  • One way only. Jasper never changes anything in Postman.
  • Scripts sync at collection, folder and request level. The desktop app runs them in Postman's own script engine; monitors on the web run a subset of pm.*.
  • An item deleted in Postman is marked [Removed] in Jasper, not deleted. An item you delete in Jasper is not brought back.
  • A collection deleted in Postman stops syncing but stays in Jasper.
  • Sync pauses until next month when less than 10% of the key's monthly Postman API quota is left.
  • OAuth 2.0 settings are kept, but Jasper doesn't fetch OAuth 2.0 tokens when it sends a request.

Common questions

Does Jasper change anything in Postman?

No. Sync is one way, from Postman to Jasper.

What happens to my edits in Jasper?

They are kept. A sync only updates a field that still matches what the last sync wrote.

How often does it sync?

Every 15, 30, 60, 120 or 240 minutes: the shortest of these that keeps a month without changes within a quarter of the key's monthly Postman API quota. It never waits longer than 4 hours, so a small quota with many workspaces can use more. Sync now checks straight away.

Who can see synced collections?

Everyone in your Jasper organisation. Environments stay private to you, and secrets go into your own encrypted environment.

Can I import a Postman file instead?

Yes. The API client imports Postman v2.0 and v2.1 collections and environments, and OpenAPI 3.0, 3.1 and Swagger 2.0 files. It exports Postman v2.1.

Can I connect more than one Postman account?

Yes, for example another team's key. Each connection syncs the workspaces you pick for it.

Guides

Works with

Compare

Other integrations

Checked against the product on 4 October 2026.