# Integrating SailPoint with AlertOps

AlertOps is an incident alerting platform that helps organizations detect, route, and respond to operational incidents across teams and systems. It provides on-call scheduling, escalation policies, and notification workflows so responders receive timely alerts through the channels they use. This document provides the instructions required to configure a new direct connection between SailPoint and AlertOps. 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 AlertOps connector supports the following:

### Account Management

- Aggregate Accounts

### Entitlement Management

- Aggregate Roles and Groups

> [!NOTE]
>
> This connector is read-only. It supports account and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported.

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

### Pagination

The AlertOps source uses numeric offset-based pagination rather than cursor-based paging. Each request accepts `offset` and `limit` query parameters. The connector starts at offset `0` and increments the offset after each request. Aggregation continues until the number of records returned is less than the configured page `limit`, at which point aggregation terminates.

#### How Pagination Works for This Operation

- **Initial Page Offset:** `0` - starting point for the first request (AlertOps offsets are 0-indexed).
- **Page Size:** `100` - number of records requested per page, passed via the `limit` query parameter (default value is `10`).

Paging steps:

- `$limit$` = `100`
- `TERMINATE_IF $RECORDS_COUNT$ < $limit$`
- `$offset$` = `$offset$ + 1`
- `$endpoint.fullUrl$` = `$application.baseUrl$` + `"/users?include=roles&offset=" + $limit$ + "&offset=" + $offset$`

## Prerequisites

Before configuring the AlertOps connector, ensure the following requirements are met:

1. Sign in to AlertOps at `https://app.alertops.com`.
2. Go to **User Profile** to retrieve your **User API Key**.

   - **Base URL** - `https://api.alertops.com/api/v2` (REST endpoint)
   - **User API Key** - used in the `api-key` request header for all API calls. AlertOps does not use Basic authentication.
3. Pass the API key in the `api-key` header for every request:

```text
api-key: <your_user_api_key>
```

For more detailed information on obtaining a User API Key and using the Users API, refer to the official AlertOps API documentation: [AlertOps Users API](<https://api.alertops.com/help/index.html?url=/swagger/v2/swagger.json#/Users/Users_GetUser>).

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

## Required Permissions

- **Owner** - Full administrative access to the AlertOps organization, including user and group management.
- **Billing Admin** - Administrative access to billing and account settings with visibility into organizational users.
- **System Viewer** - Read-only access to system configuration and user directory data required for aggregation.
- **Send Message** - Permission to interact with messaging features; included as a standard role in the AlertOps platform.