Skip to content

Integrating SailPoint with Spike

Spike is an on-call and incident management platform that creates incidents from monitoring alerts, pages responders, and escalates until someone responds. This document covers how to configure a new direct connection between SailPoint and Spike for Quick Compliance. For a reference to the terminology specific to SailPoint products, refer to Source and Connector Definitions.

Note

To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the SaaS Release Notes page.

Supported Features

The Spike connector supports the following:

Account Management

  • Aggregate Users

Entitlement Management

  • Aggregate Teams

Non-Human Identity Discovery

  • Aggregate Integrations

Refer to Dataset Management for more information.

Refer to Discovering Potential Non-Human Accounts for more information.

Note

This connector is read-only. It supports test connection, account aggregation, entitlement aggregation, and dataset aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported. The member role is collected on the account.

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

Before you configure the Spike connector, ensure the following requirements are met:

  1. Sign in to the Spike dashboard.
  2. Go to Settings > API.
  3. Generate an API key. Copy the key and store it securely.

  4. Record the following values for connector configuration:

    • Base URL
    • API Key

Important

The API key has full organization API access. Granular permissions are not supported. If you replace the key, update every SailPoint source that uses the previous key.

For more information, refer to the Spike API documentation.

Note

The linked document is not maintained by SailPoint and is subject to change without notice.

Required Permissions

Generate the API key from an Admin account. The connector can read the organization data available to that key.