---
title: 'Splunk On-Call'
description: 'Manage incidents, on-call schedules, and teams with Splunk On-Call (VictorOps).'
---

# Splunk On-Call

Manage incidents, on-call schedules, and teams with Splunk On-Call (VictorOps).

| Detail | Value |
|---|---|
| Category | Monitoring |
| Base URL | `https://api.victorops.com/api-public/v1` |
| Authentication | Bearer Token |
| Endpoints | 8 |
| Connector key | `victorops` |

## Using Splunk On-Call in a workflow

1. Go to **Connections** and click **New Connection**.
2. Pick **Splunk On-Call** from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an **API Call** node and select this connection.
5. Pick the operation you need from the Operation dropdown — see the table below.

## Available Endpoints

| Endpoint | Summary |
|---|---|
| [GET /incidents](./get_incidents_monitoring_listincidents) | List incidents |
| [PATCH /incidents/resolve](./patch_incidents_resolve_monitoring_resolveincidents) | Resolve incidents |
| [PATCH /incidents/ack](./patch_incidents_ack_monitoring_acknowledgeincidents) | Acknowledge incidents |
| [GET /team](./get_team_monitoring_listteams) | List teams |
| [GET /team/{team}/oncall/schedule](./get_team_team_oncall_schedule_monitoring_getteamoncallschedule) | Get on-call schedule |
| [GET /oncall/current](./get_oncall_current_monitoring_getcurrentoncall) | Get current on-call |
| [GET /user](./get_user_monitoring_listusers) | List users |
| [GET /alerts](./get_alerts_monitoring_listalerts) | List alerts |

> Each endpoint has its own page with parameter details, an example
> `API Call` node configuration, and the response shape.