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 — the full list is below.

Available endpoints

Endpoint	Summary
GET /incidents	List incidents
PATCH /incidents/resolve	Resolve incidents
PATCH /incidents/ack	Acknowledge incidents
GET /team	List teams
GET /team/{team}/oncall/schedule	Get on-call schedule
GET /oncall/current	Get current on-call
GET /user	List users
GET /alerts	List alerts

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /incidents

List incidents

Detail	Value
Operation ID	monitoring.listIncidents
Method	GET
Path	/incidents

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Splunk On-Call connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listIncidents.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Splunk On-Call API reference.

PATCH /incidents/resolve

Resolve incidents

Detail	Value
Operation ID	monitoring.resolveIncidents
Method	PATCH
Path	/incidents/resolve

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Splunk On-Call connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.resolveIncidents.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Splunk On-Call API reference.

PATCH /incidents/ack

Acknowledge incidents

Detail	Value
Operation ID	monitoring.acknowledgeIncidents
Method	PATCH
Path	/incidents/ack

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Splunk On-Call connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.acknowledgeIncidents.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Splunk On-Call API reference.

GET /team

List teams

Detail	Value
Operation ID	monitoring.listTeams
Method	GET
Path	/team

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Splunk On-Call connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listTeams.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Splunk On-Call API reference.

GET /team/{team}/oncall/schedule

Get on-call schedule

Detail	Value
Operation ID	monitoring.getTeamOnCallSchedule
Method	GET
Path	/team/{team}/oncall/schedule

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Splunk On-Call connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.getTeamOnCallSchedule.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Splunk On-Call API reference.

GET /oncall/current

Get current on-call

Detail	Value
Operation ID	monitoring.getCurrentOnCall
Method	GET
Path	/oncall/current

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Splunk On-Call connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.getCurrentOnCall.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Splunk On-Call API reference.

GET /user

List users

Detail	Value
Operation ID	monitoring.listUsers
Method	GET
Path	/user

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Splunk On-Call connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listUsers.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Splunk On-Call API reference.

GET /alerts

List alerts

Detail	Value
Operation ID	monitoring.listAlerts
Method	GET
Path	/alerts

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Splunk On-Call connection from the Connection dropdown.
3. In the Operation dropdown, select monitoring.listAlerts.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Splunk On-Call API reference.