Automate VictorOps

What VictorOps is

This API allows you to interact with the VictorOps platform in various ways. Your account may be limited to a total number of API calls per month. Also, some of these API calls have rate limits. NOTE: In this documentation when creating a sample curl request (clicking the TRY IT OUT! button), in some API viewing interfaces, the '@' in an email address may be encoded. Please note that the REST endp

API host: api.victorops.com

What HumDay can do in VictorOps

32 documented operations change something in VictorOps.

• POSTAdd a user/api-public/v1/user
• POSTCreate a contact emails for a user/api-public/v1/user/{user}/contact-methods/emails
• POSTCreate a new incident/api-public/v1/incidents
• POSTCreates a new scheduled override/api-public/v1/overrides
• DELETEDelete a contact email for a user/api-public/v1/user/{user}/contact-methods/emails/{contactId}
• DELETERemove a user/api-public/v1/user/{user}
• PUTUpdate a user/api-public/v1/user/{user}
• POSTCreate a contact phones for a user/api-public/v1/user/{user}/contact-methods/phones
• POSTAdd a team/api-public/v1/team
• PATCHAcknowledge an incident or list of incidents/api-public/v1/incidents/ack
• POSTReroute one or more incidents to one or more new routable destinations./api-public/v1/incidents/reroute
• PATCHResolve an incident or list of incidents/api-public/v1/incidents/resolve
• PATCHCreate an on-call override (take on-call)/api-public/v1/policies/{policy}/oncall/user
• PATCHAcknowledge all incidents for which a user was paged./api-public/v1/incidents/byUser/ack
• PATCHResolve all incidents for which a user was paged./api-public/v1/incidents/byUser/resolve
• POSTAdd a team member/api-public/v1/team/{team}/members
• POSTCreate a paging policy step/api-public/v1/profile/{username}/policies
• DELETEDelete a contact phone for a user/api-public/v1/user/{user}/contact-methods/phones/{contactId}
• DELETEDelete a contact device for a user/api-public/v1/user/{user}/contact-methods/devices/{contactId}
• PUTUpdate a contact device for a user/api-public/v1/user/{user}/contact-methods/devices/{contactId}
• POSTStart maintenance mode for routing keys/api-public/v1/maintenancemode/start
• DELETERemove a team/api-public/v1/team/{team}
• PUTUpdate a team/api-public/v1/team/{team}
• DELETEDeletes a scheduled override/api-public/v1/overrides/{publicId}
• DELETERemove a team member/api-public/v1/team/{team}/members/{user}
• POSTCreate a rule for a paging policy step/api-public/v1/profile/{username}/policies/{step}
• PUTEnd maintenance mode for routing keys/api-public/v1/maintenancemode/{maintenancemodeid}/end
• PUTUpdate a paging policy step/api-public/v1/profile/{username}/policies/{step}
• DELETEDelete the scheduled override assignment/api-public/v1/overrides/{publicId}/assignments/{policySlug}
• PUTUpdate the scheduled override assignment/api-public/v1/overrides/{publicId}/assignments/{policySlug}
• DELETEDelete a rule from a paging policy step/api-public/v1/profile/{username}/policies/{step}/{rule}
• PUTUpdate a rule for a paging policy step/api-public/v1/profile/{username}/policies/{step}/{rule}

What HumDay can read from VictorOps

These are the operations a schedule or a trigger can watch.

• GETList users/api-public/v1/user
• GETGet a list of all contact emails for a user/api-public/v1/user/{user}/contact-methods/emails
• GETGet a list of all contact methods for a user/api-public/v1/user/{user}/contact-methods
• GETGet the indicated contact email for a user/api-public/v1/user/{user}/contact-methods/emails/{contactId}
• GETRetrieve information for a user/api-public/v1/user/{user}
• GETGet a list of all contact phones for a user/api-public/v1/user/{user}/contact-methods/phones
• GETGet a list of all contact devices for a user/api-public/v1/user/{user}/contact-methods/devices
• GETGet the available contact types/api-public/v1/policies/types/contacts
• GETList teams/api-public/v1/team
• GETList the scheduled overrides/api-public/v1/overrides
• GETRetrieve the user's team membership/api-public/v1/user/{user}/teams
• GETGet/search incident history/api-reporting/v2/incidents
• GETGet a list of paging policies for a user/api-public/v1/user/{user}/policies
• GETGet an organization's on-call users/api-public/v1/oncall/current
• GETList routing keys with associated teams/api-public/v1/org/routing-keys
• GETGet a user's on-call schedule/api-public/v2/user/{user}/oncall/schedule
• GETGet escalation policy info/api-public/v1/policies
• GETGet the available notification types/api-public/v1/policies/types/notifications
• GETGet current incident information/api-public/v1/incidents
• GETRetrieve a list of team admins for a team/api-public/v1/team/{team}/admins
• GETRetrieve a list of members for a team/api-public/v1/team/{team}/members
• GETGet an organization's current maintenance mode state/api-public/v1/maintenancemode
• GETRetrieve a list of escalation policies for a team/api-public/v1/team/{team}/policies
• GETGet the user's paging policy/api-public/v1/profile/{username}/policies
• GETGet the indicated contact phone for a user/api-public/v1/user/{user}/contact-methods/phones/{contactId}
• GETGet the indicated contact device for a user/api-public/v1/user/{user}/contact-methods/devices/{contactId}
• GETA list of shift changes for a team/api-reporting/v1/team/{team}/oncall/log
• GETGet a team's on-call schedule/api-public/v2/team/{team}/oncall/schedule
• GETRetrieve information for a team/api-public/v1/team/{team}
• GETRetrieve alert details./api-public/v1/alerts/{uuid}
• GETGet the specified scheduled override/api-public/v1/overrides/{publicId}
• GETGet the available timeout values/api-public/v1/policies/types/timeouts
• GETGet the specified scheduled override/api-public/v1/overrides/{publicId}/assignments
• GETGet a paging policy step/api-public/v1/profile/{username}/policies/{step}
• GETGet the specified scheduled override assignment/api-public/v1/overrides/{publicId}/assignments/{policySlug}
• GETGet a rule from a paging policy step/api-public/v1/profile/{username}/policies/{step}/{rule}

How automating VictorOps works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
3. See it proven. The program runs and shows you the result before it is allowed near your live VictorOps account.
4. Grant access, then go live. You approve the specific VictorOps operations it may use — and only those.

Automate VictorOps with these

• OData for namespace microsoft.graph11412 operations
• GitHub811 operations
• Atlassian The Jira Cloud platform474 operations
• Gitlab358 operations
• JIRA 7.6.1324 operations
• Appcenter App Center Client323 operations
• Gitea .321 operations
• Bitbucket292 operations
• Keycloak Admin281 operations
• Apple App Store Connect251 operations
• Files.com222 operations
• Vmware vRealize Network Insight Reference161 operations

Categories

• Developer tools

Questions about VictorOps automation

Can HumDay connect to VictorOps?

Yes. HumDay reads VictorOps's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 68 operations are documented.

Do I need to write code to automate VictorOps?

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

What can HumDay do in VictorOps?

32 of the 68 documented operations change something in VictorOps, and 36 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my VictorOps account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to VictorOps is held behind that approval.

Where this came from

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