VictorOps
VictorOps REST Endpoint allows you to send customized alerts and incident details into the VictorOps timeline. Alerts get sent into the VictorOps incident workflow with fields such as message_type, entity_id, and/or state_message. As these alerts come into VictorOps, they are routed directly to the proper person or team with incident details that give the on-call responder more context.Current Version: 1.0.0
Publisher: Toro Cloud
22Get it now Rate it
VictorOps REST Endpoint Establishes Incident Lifecycle Workflows
- Send alerts straight into VictorOps with detailed incident context
- Collaborate around issues in the VictorOps timeline via incident prioritization, escalation, native chat, runbook links, and more
- Remediate incidents more quickly with automated contextual alerting, communication, and incident workflow management in one centralized location
The VictorOps REST Endpoint accepts alerts from any source via an HTTPS POST request in JSON format. As long as you can configure the content of the request, you can trigger, acknowledge, or resolve incidents in VictorOps.
Enable the RES
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 endpoints will not
process the encoded version. Make sure that the encoded character '%40' is changed to its unencoded form before
submitting the curl request.
Licensed under MIT.
Categories:
Compatibility:
Resources:
License:
API Specification: Swagger 2.x
Schema Source: TORO Docs to OpenAPI
Tags: notification, messaging
| Version | API Reference Version | Compatibility | Date added | Summary | |
|---|---|---|---|---|---|
| 1.0.0 | --- | --- | 2019-11-25 |
No reviews yet