Postman Monitor Iteration Count UI vs API Behavior

Direct Answer

No. The Postman UI does not automatically enforce an API-defined iterationCount when you open or save a monitor created through the API. A monitor created through Postman API v2 with iterationCount greater than 1 retains that stored value when viewed in the UI editor, because the editor has no iteration-count input and opening the monitor does not rewrite it. However, saving any change through the UI may reset iterationCount to 1 if the UI’s update request omits the field. Whether that reset happens depends on your Postman app version and is not confirmed by published Postman behavior.

Confirmed Facts vs Likely Behavior

Confirmed

• Postman API v2 supports iterationCount on monitor creation and updates.
• Omitting iterationCount normally defaults the monitor to one iteration per scheduled run.
• The Postman monitor UI editor has no explicit iteration-count input.
• A monitor built only in the UI cannot set an API-defined iteration override directly.

Likely or Unconfirmed

• An API-created monitor with iterationCount greater than 1 keeps that value until an API or UI update changes it.
• Opening the monitor in the UI does not by itself change the stored iterationCount.
• Editing and saving in the UI may reset iterationCount to 1 if the UI update omits the field; verify this against your Postman version before relying on UI edits.

Steps for This Case

1. Create the monitor through the API with iterationCount set to the desired value, for example 3.
2. Call GET /monitors/{monitorId} and confirm the returned iterationCount matches.
3. Run the monitor once and confirm the execution performs the expected number of collection iterations.
4. If you must edit the monitor in the UI, change only non-iteration fields, save, then immediately call GET /monitors/{monitorId} again and compare iterationCount before and after.
5. If the UI save reset the value, reapply the desired value through the API with PATCH /monitors/{monitorId} and the iterationCount field.

Missing Diagnostic Detail

One detail changes whether UI edits are safe: does the UI’s monitor-save request include the current iterationCount? Capture the network request when saving a monitor in the UI and inspect the request body. If it omits iterationCount, treat UI saves as destructive to API-set values and manage iterationCount exclusively through the API.

Assumptions and Version Notes

This answer assumes Postman Monitor version 10.x and Postman API v2. A higher iterationCount increases scheduled run time and may affect monitor limits or billing; confirm against your Postman plan. Postman UI behavior can change between app versions, so re-confirm API field semantics for your current release.

Safe Verification Commands

# Read-only check
curl -H "X-Api-Key: $POSTMAN_API_KEY" \
  https://api.getpostman.com/monitors/{monitorId}

# Scoped update: reapply iterationCount only
curl -X PATCH -H "X-Api-Key: $POSTMAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"monitor":{"iterationCount":3}}' \
  https://api.getpostman.com/monitors/{monitorId}