# Integrating SailPoint with Splunk On-Call (previously VictorOps)

Splunk On-Call (previously VictorOps) is an incident management and response automation platform designed for DevOps and SRE teams. It enables teams to centralize alerts, automate on-call rotations, engage the right people, and streamline incident resolution through a powerful combination of incident management, on-call scheduling, and collaboration tools. This document provides instructions to configure a new direct connection between SailPoint and Splunk On-Call. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The Splunk On-Call connector supports the following:

### Account Management

- Aggregate Active Users

### Entitlement Management (Teams)

- Aggregate Teams

### Supported Managed Systems

- Splunk On-Call

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

## Prerequisites

Ensure the following prerequisites are met before proceeding with the configuration:

- Generate the **API Key** and the **Access Key** for the super admin user account.

  > **Resource Link**
  >
  > [API Calls in Splunk On-Call | Splunk On-Call Software](<https://help.victorops.com/knowledge-base/api/>)

  > **Note**
  >
  > - An administrative user must have super admin role to authenticate.
  > - User needs to provide both the **API ID** and the **API Key**.