# Integrating SailPoint with Givebutter

Givebutter is a cloud-based fundraising and donor/constituent management platform used by nonprofits and community organizations to manage contacts (donors, volunteers, sponsors), campaigns, transactions, and recurring giving. It lets organizations track contact relationships - including companies a contact is associated with, their donation history, and communication preferences - and connects to other tools via its REST API using API key (Bearer token) authentication. This document provides instructions to configure a new direct connection to a Givebutter 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 Givebutter connector supports the following:

### Account Management

- Aggregate Contacts

> [!NOTE]
>
> A contact's company affiliations are captured as part of the Account aggregation itself (embedded within each contact record as the `associated_companies` array), so a separate Entitlement aggregation is not required. `associated_companies_name` is used as the Entitlement value.

> [!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. Sign in to [Givebutter](<https://givebutter.com/>).
2. Go to **Settings \> Developers \> API \> New API key**.
3. Copy and securely store the following details, which are required during connector configuration:

   - **API Key**

> [!NOTE]
>
> The Givebutter API uses Bearer token authentication: `Authorization: Bearer {{ your_api_key }}`. No additional custom headers are required for the Contacts endpoint. All API requests must be made over HTTPS; unencrypted HTTP calls are not supported and will fail. Tokens should be stored securely and treated like a password.

## Required Permissions

Givebutter uses role-based access. Available roles:

- **Administrator** - full access to all features, settings, billing, team management
- **Finance** - payouts, refunds, transactions, financial reports
- **Campaign Editor** - create/manage campaigns, events, fundraising pages
- **CRM Manager** - manage contacts, segments, communications
- **Mobile Access** - Full (contacts, transactions, invites) or Limited (check-in/events only)

For detailed information on Givebutter API authentication, refer to the [Givebutter API documentation](<https://docs.givebutter.com/api-reference/>).

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