Get the user's paging policy in VictorOps
A documented VictorOps operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get the user's paging policy
- GETReads data · Personal Paging Policies
api.victorops.com/api-public/v1/profile/{username}/policies
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which VictorOps operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
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
Questions
- Can HumDay get the user's paging policy 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.
- Does this change anything in my VictorOps account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in VictorOps.
- 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.