Skip to content
Start in the sandboxStart free
All connectors
Postman logo

Postman

Software delivery, ITSM & observability

Turn incidents and requests into Postman work items, and keep status in step across your tools.

19 ways to read, 4 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Postman with Nexra

Connected, approved, proven.

The things teams do most with Postman, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Create empty API collectionApproval by rule
  • Create environmentApproval by rule
  • Read API collectionsRead

Example flow

  1. Postman · Read API collectionsDone
  2. Postman · Create empty API collectionNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Postman.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to Postman
  • Postman's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Read Postman workspaces, collections, environments, APIs and versions, mocks, monitors, team users and team audit logs; create and update collections and environments.

Postman API docs
Source actions
19
Destination actions
4
Data types
11

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

API collections4
  • Create empty API collectionDestinationNot retried automaticallyApproval before production

    Create a named collection in the selected workspace; does not execute requests or scripts.

  • Get API collectionSource

    Read a collection's metadata, top-level folders and requests, and variable names.

  • Read API collectionsSource

    Read collection names and identifiers visible to this API key in the selected workspace.

  • Update API collectionDestinationProvider duplicate protectionApproval before production

    Rename a collection or change its description. Requests are not touched.

API versions2
  • Get API versionSource

    Read one API version with its release notes, schemas and collections.

  • List API versionsSource

    List the published versions of an API.

APIs2
  • Get APISource

    Read an API with its linked collections, versions and schemas.

  • List APIsSource

    List the APIs defined in the selected workspace.

Audit logs1
  • List team audit logsSourceIncremental

    List audit events for the Postman team (who did what, and when), newest first. Postman keeps 180 days of audit logs.

Current user1
  • Get authenticated userSource

    Read the user and team that own this API key.

Environments4
  • Create environmentDestinationNot retried automaticallyApproval before production

    Create an environment with variables in the selected workspace.

  • Get environmentSource

    Read an environment's name and variable names, types and enabled flags.

  • List environmentsSource

    List environments in the selected workspace.

  • Replace environmentDestinationProvider duplicate protectionApproval before production

    Replace an environment's name and all of its variables. Variables you leave out are removed.

Mocks2
  • Get mock serverSource

    Read a mock server's URL, collection and environment.

  • List mock serversSource

    List active mock servers in the selected workspace.

Monitor runs1
  • Get latest monitor runSource

    Read the latest run of a monitor: status, timings, and test and request counts.

Monitors2
  • Get monitorSource

    Read a monitor's schedule, collection, environment and last run status.

  • List monitorsSource

    List monitors in the selected workspace.

Team users2
  • Get team userSource

    Read one team user's name, email, roles and join date.

  • List team usersSource

    List users on the Postman team with their roles.

Workspaces2
  • Get workspaceSource

    Read a workspace with its collections, environments, mocks and monitors. Defaults to the connection's workspace.

  • List workspacesSource

    List the workspaces this API key can access.

Access and limits

Authentication
Postman API key
Plans and access
Postman account with API allowance. Team users and some workspace types need a team plan. Key owner needs access to the selected workspace, and Editor rights to create or update collections and environments.
Test environment
Use a dedicated development workspace, not production collections.
Rate limits
Respect Postman API plan limits (monthly usage and per-minute limits) and 429 Retry-After responses.
Pagination
Collection lists use limit/offset; workspaces, APIs, API versions and monitors use meta.nextCursor; audit logs use nextCursor; environments, mocks and team users return one page.
Provider events
Postman webhooks are not used by these operations. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Collection reads return metadata, top-level folder and request names, and variable names only: no request bodies, auth, scripts or variable values.
  • Environment reads return variable names, types and enabled flags only; values are never read back.
  • Collection and environment creation is not idempotent; reconcile a timeout before retrying.
  • Environment update replaces all variables (PUT). Collection update changes the name and description only; replacing collection contents is excluded.
  • Deletes, forks, merges, publishing, running monitors, monitor and mock writes, and workspace changes are intentionally excluded.
  • Monitor runs: the Postman API exposes the latest run per monitor, so run history is not available.
  • Mock call logs are excluded because they can contain captured request headers and bodies.
  • Only the US API origin (api.postman.com) is supported; EU data-residency teams (api.eu.postman.com) are not.
  • An invalid workspace may return an empty list; a successful connection test confirms API-key access, not workspace ownership.

Developer reference

  1. Create the Postman credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Postman, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
Postman docsAPI referencePostman docsAuthenticationPostman docsRate limits

Machine-readable detail: GET /api/public/connect/connectors/postman and the Connections API.