# Integrating SailPoint with Incident.io

Incident.io is a modern incident management platform that integrates with your existing tools to streamline incident response, on-call scheduling, and post-incident analysis. By leveraging the Incident.io Developer API, organizations can orchestrate user discovery, track administrative permissions, and audit active users within the platform. This document provides instructions to configure a new direct connection to an Incident.io source. 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 Incident.io connector supports the following:

### Account Management

- Aggregate Users

> [!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:

1. Ensure you have an active Incident.io account with **Owner** permissions (or a custom role with `Manage API` keys privileges).
2. Go to **Settings \> API keys** in the Incident.io dashboard.
3. Select **Create API key** and assign standard **Read users** (**account-level**) permission.
4. Copy the generated **API Key** and store it in a secure location (it will only be shown once). For more information about managing API keys and permissions, refer to the [Incident.io API Keys documentation](<https://docs.incident.io/admin/api-keys>).

## Required Permissions

- Your service account/API key must have sufficient read permissions to query the organization’s user directory. At a minimum, the key should have read access to the standard account resources to pull metadata about the users, their assigned roles, and their seat types.
- The API uses key-based bearer authentication. There are no granular scopes defined per endpoint, but API keys are restricted to the level of access granted to the user who created them.
- For more information about endpoint structures and authentication, refer to the following resources:

  - [Incident.io API Reference Introduction](<https://docs.incident.io/api-reference/introduction>)
  - [Incident.io User Roles and Permissions documentation](<https://docs.incident.io/admin/user-permissions>)

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.