Update a rule for a paging policy step in VictorOps

What this operation does

Update a rule for a paging policy step

• PUTChanges data · Personal Paging Policiesapi.victorops.com/api-public/v1/profile/{username}/policies/{step}/{rule}

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 VictorOps 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 VictorOps operations

• Create a contact emails for a userPOST · changes data
• Create a new incidentPOST · changes data
• Creates a new scheduled overridePOST · changes data
• Delete a contact email for a userDELETE · changes data
• Remove a userDELETE · changes data
• Update a userPUT · changes data
• Create a contact phones for a userPOST · changes data
• Acknowledge an incident or list of incidentsPATCH · changes data

All 68 VictorOps operations

Questions

Can HumDay update a rule for a paging policy step in VictorOps?

Yes. This operation is published in VictorOps'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 VictorOps data?

Yes — this is a PUT operation, so it changes something in VictorOps. 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 VictorOps account.

Where this came from

Read from a published API description for VictorOps at portal.victorops.com/public/api-docs/victorops-api-v1.yaml. The description above is the provider’s own wording, not ours. Last published 2019-07-22.