VictorOps
  1. Reporting
VictorOps
  • Alerts
    • Retrieve alert details.
      GET
  • Incidents
    • Get current incident information
      GET
    • Create a new incident
      POST
    • Acknowledge an incident or list of incidents
      PATCH
    • Acknowledge all incidents for which a user was paged.
      PATCH
    • Resolve all incidents for which a user was paged.
      PATCH
    • Reroute one or more incidents to one or more new routable destinations.
      POST
    • Resolve an incident or list of incidents
      PATCH
  • Maintenance Mode
    • Get an organization's current maintenance mode state
      GET
    • Start maintenance mode for routing keys
      POST
    • End maintenance mode for routing keys
      PUT
  • On-call
    • Get an organization's on-call users
      GET
    • Create an on-call override (take on-call)
      PATCH
    • Get a team's on-call schedule
      GET
    • Create an on-call override (take on-call)
      PATCH
    • Get a user's on-call schedule
      GET
    • Get a team's on-call schedule
      GET
    • Get a user's on-call schedule
      GET
  • Routing Keys
    • List routing keys with associated teams
      GET
  • Scheduled Overrides
    • List the scheduled overrides
      GET
    • Creates a new scheduled override
      POST
    • Deletes a scheduled override
      DELETE
    • Get the specified scheduled override
      GET
    • Get the specified scheduled override
      GET
    • Delete the scheduled override assignment
      DELETE
    • Get the specified scheduled override assignment
      GET
    • Update the scheduled override assignment
      PUT
  • Escalation Policies
    • Get escalation policy info
    • Retrieve a list of escalation policies for a team
  • Personal Paging Policy Values
    • Get the available contact types
    • Get the available notification types
    • Get the available timeout values
  • Personal Paging Policies
    • Get the user's paging policy
    • Create a paging policy step
    • Get a paging policy step
    • Create a rule for a paging policy step
    • Update a paging policy step
    • Delete a rule from a paging policy step
    • Get a rule from a paging policy step
    • Update a rule for a paging policy step
  • Teams
    • List teams
    • Add a team
    • Remove a team
    • Retrieve information for a team
    • Update a team
    • Retrieve a list of team admins for a team
    • Retrieve a list of members for a team
    • Add a team member
    • Remove a team member
  • Users
    • List users
    • Add a user
    • Remove a user
    • Retrieve information for a user
    • Update a user
    • Retrieve the user's team membership
  • User Contact Methods
    • Get a list of all contact methods for a user
    • Get a list of all contact devices for a user
    • Delete a contact device for a user
    • Get the indicated contact device for a user
    • Update a contact device for a user
    • Get a list of all contact emails for a user
    • Create a contact emails for a user
    • Delete a contact email for a user
    • Get the indicated contact email for a user
    • Get a list of all contact phones for a user
    • Create a contact phones for a user
    • Delete a contact phone for a user
    • Get the indicated contact phone for a user
  • User Paging Policies
    • Get a list of paging policies for a user
  • Reporting
    • Get/search incident history
      GET
    • A list of shift changes for a team
      GET
    • Get/search incident history
      GET
  1. Reporting

Get/search incident history

Deprecated
GET
/api-reporting/v1/incidents
NOTE: This call is deprecated. Please use GET /api-reporting/v2/incidents.
Retrieve incident history for your company, searching over date ranges and with filtering options. This is historical
data, and may be up to 15 minutes behind real-time incident data. By default, only resolved incidents will be returned.
This API may be called a maximum of once a minute.
Incident requests are paginated with a offset and limit query string parameters.
The query for incidents is run and offset records are skipped, after which limit records will be returned.
The default offset is 0 and the default limit is 20. The maximum value allowed for limit is 100.
On return, the total number of records available for that query will be returned in the payload as 'total'.
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request GET 'https://api.victorops.com//api-reporting/v1/incidents' \
--header 'X-VO-Api-Id;' \
--header 'X-VO-Api-Key;'
Response Response Example
200 - Example 1
[
    {
        "incidents": [
            {
                "ackTime": "string",
                "ackUser": {
                    "email": "string",
                    "first": "string",
                    "last": "string"
                },
                "ackUserId": "string",
                "alertCount": 0,
                "currentPhase": "string",
                "endTime": "string",
                "entityDispName": "string",
                "entityId": "string",
                "entityType": "string",
                "host": "string",
                "incidentNumber": "string",
                "lastAlertID": "string",
                "lastAlertTime": "string",
                "service": "string",
                "startTime": "string",
                "teams": "string"
            }
        ],
        "limit": 0,
        "offset": 0,
        "total": 0
    }
]

Request

Query Params

Header Params

Responses

🟢200The list of incidents matching the request filters
application/json
Body

🟠400400
🟠401401
🟠403403
🟠404404
🔴500500
Modified at 2022-09-10 22:14:55
Previous
Get a list of paging policies for a user
Next
A list of shift changes for a team
Built with