Update Collection in Getpostman Postman

What this operation does

Update Collection

• PUTChanges data · Collectionsapi.getpostman.com/collections/{collection_uid}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which Getpostman Postman operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other Getpostman Postman operations

• Create WebhookPOST · changes data
• Create MonitorPOST · changes data
• Create WorkspacePOST · changes data
• Create CollectionPOST · changes data
• Create EnvironmentPOST · changes data
• Create API VersionPOST · changes data
• Create a ForkPOST · changes data
• Import external API specificationPOST · changes data

All 57 Getpostman Postman operations

Questions

Can HumDay update collection in Getpostman Postman?

Yes. This operation is published in Getpostman Postman's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my Getpostman Postman data?

Yes — this is a PUT operation, so it changes something in Getpostman Postman. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Getpostman Postman account.

Where this came from

Read from a published API description for Getpostman Postman at gist.githubusercontent.com/MikeRalphson/f5dd7e7e712a4f2caa8f1783f1053dbc/raw/05fb7ae8b877b. The description above is the provider’s own wording, not ours. Last published 2021-06-21.