Reuse API collections
3 minute read · API Client
Reuse requests you already have, then check their targets and credentials before running them. Importing a collection is not permission to send every request in it.
- Import a collection you can understand
- Share the useful structure
- Resolve shared edits without losing a draft
- Review an imported collection before the first send
- Collection transfer and sharing controls
Import a collection you can understand
Choose a supported Postman collection JSON or Vortex collection shape, or parse a supported cURL request. Inspect the imported folder/request structure, methods, body types, authorization and scripts before sending anything. Variables default to local-only; decide explicitly which values belong in cloud synchronization.
Start by sending one known read-only request to a development endpoint. Verify its resolved URL and response, then inspect more complex auth/script flows. Import support is not a promise that every Postman extension, cookie behavior or script API is reproduced without adjustment.
Share the useful structure
A cluster can use the existing owner/editor/viewer roles, invitations and private/public/unlisted visibility paths. Choose the audience intentionally. A public collection can explain endpoints with placeholder variables while keeping live credentials private. Unlisted visibility should not be mistaken for a secret-management system.
Before exporting, inspect what values and scripts will be included. Remove private tokens and customer examples from the exported artifact. Opening tabs leaves the saved collection unchanged; cloning or importing creates another saved cluster. Give imported copies clear names so you can distinguish their environment and ownership.
Resolve shared edits without losing a draft
When a remote revision changes during local editing, keep the unsaved request and compare versions. A failed save should leave the working draft available. Do not repeatedly overwrite the shared version to dismiss a conflict indicator. Check your role if the save is read-only or denied.
Shared membership grants access to the selected collection, not to another account's personal workspace records or Vault secrets. Read account access when a shared action is unavailable.
Review an imported collection before the first send
Import a supported Postman collection or Vortex export, or parse a cURL request. Inspect the created folder/request structure, methods, destinations, bodies, scripts and inherited authorization. Importing is a way to prepare requests; it is not authorization to send them to the original author's live service.
Create your own local environment and supply credentials through the appropriate private fields. Check which variables are local-only before cloud synchronization or export. Choose private, public or unlisted visibility deliberately and confirm whether a collaborator has owner, editor or viewer access. An unlisted link is still something a recipient can forward.
For concurrent edits, keep your unsaved tab when a cloud revision conflicts. Compare the saved revision with the draft, merge the intended changes and save again. Do not repeatedly overwrite the cloud just to dismiss a conflict. Authentication and environments covers avoiding accidental credential sharing.
Related guides: environment privacy, response checks.
Collection transfer and sharing controls
| Action | What to check |
|---|---|
| Import | Choose the supported collection/file/cURL format, inspect the destination cluster and read validation errors. Importing definitions does not automatically execute every request. |
| Export | Select the intended scope and output format. Inspect auth, cookies, variables and scripts before giving the file to someone else. |
| Share / invitations | Select the target collection/workspace and the permissions offered by the sharing flow. |
| Accept invitation | Joins the resource with the role granted by its owner; it does not make you its owner. |
| Local / shared variable values | Decide which values stay on this machine and which are available to collaborators. Imports default variables to local-only. |
| Remove / leave shared resource | Applies the specific ownership/membership action shown by the UI. Read whether it removes your access or deletes the resource. |
Reopen an imported read-only request, verify its resolved URL/authentication and send it once. Import compatibility varies by the source's script and authentication extensions. See OAuth and variable controls.