# SailPoint Infobip Connector Documentation

> Infobip Connector Documentation

# Documentation

# Connecting SailPoint and Infobip

To connect SailPoint to the source, perform the following tasks:

## Adding and Configuring the Source in SailPoint

To connect to SailPoint, perform the following steps. Once the connection is made, you can configure it to meet your company's needs.

1. Go to **Admin \> Connections \> Sources**.
2. Select **Create New**.
3. Search for a source type and select **Actions**.
4. In the **Actions** dropdown, select the setup method:

   - **Express Setup** - Quickly create a read-only connection to your target system by providing minimal configurations and authentication. On completion, aggregation is automatically started.

     > **Note**
     >
     > Express Setup supports Credential Providers. For information on supported credential providers and configuration, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>). For more information, contact your SailPoint Customer Service Manager.
   - **Standard Setup** - Provide detailed basic configuration to create the source. Once the source is created, continue with source setup.

### Express Setup

1. Review the directions and select **Start Express Setup**.
2. Review the pre-populated source name, source owner, and description. To update, select **Edit**.

   > **Note**
   >
   > Source name must be unique.
3. (Optional) If enabled for your organization, select the **Use a Credential Provider** checkbox to manage the source's authentication using a credential provider.

   > **Note**
   >
   > To add a Credential Provider in SailPoint, go to **Admin \> Connections \> Credential Providers**. For more information about credential providers, refer to [Credential Providers](<https://documentation.sailpoint.com/connectors/help/credential_providers.html>).
4. Configure the authentication to allow SailPoint to connect to the source. For more information, refer to the **Connection Settings** page.
5. Select **Finish**. After a successful test connection, the system creates your source and prompts you to run an aggregation.

   - If you want to aggregate now, select **Aggregate**.

     - To see the latest account aggregation history, go to **Account Management \> Account Aggregation**.
     - To see the list of aggregated source accounts, go to **Account Management \> Accounts**.
   - If you want to aggregate later, select **Exit**. This returns you to the **Sources** page. Your new source is listed, but contains no accounts or aggregation history yet.

### Standard Setup

Configure more detailed settings relative to Express Setup.

1. In the **Source Name** field, enter a unique and descriptive name for your source. Source names cannot exceed 128 characters.
2. In the **Description** field, provide additional details about the source to help distinguish it from similar sources. This field allows a maximum of 2,000 characters.
3. In the **Source Owner** field, begin typing the name of an owner. Matches appear after you type two or more letters. For more information, refer to [Assigning a Source Owner](<https://documentation.sailpoint.com/saas/help/sources/index.html#assigning-a-source-owner>).
4. (Optional) Select a governance group to grant its members [source](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#source-sub-admin-user-level>) or [role](<https://documentation.sailpoint.com/saas/help/common/users/user_levels.html#role-sub-admin-user-level>) sub-admin level oversight of the source and its access. For more information, refer to [Creating and Managing Governance Groups](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html>).
5. If this source represents a primary system containing your organization's personnel records, select the **Authoritative Source** checkbox. For more information, refer to [Creating Identity Profiles](<https://documentation.sailpoint.com/saas/help/setup/identity_profiles.html>).
6. Select **Continue**. The source is created, and you are navigated to the **Source Setup \> Base Configuration** page. Here, continue to configure your connected source.

## Base Configuration

Provide the base configuration parameters. Information you entered in the Create New Source dialog is automatically entered into the fields in the Base Configuration page. You can edit this information if necessary.

1. Enter a descriptive **Source Name** for the connection.
2. Enter the **Source Description** that provides details necessary to distinguish it from similar connection sources.
3. In **Source Owner**, begin typing the name of the source owner.
4. (Optional) Select the appropriate **Governance Group for Source Management** from the dropdown list. For more information about governance groups, refer to [Associating Governance Groups with a Source](<https://documentation.sailpoint.com/saas/help/common/users/governance_groups.html#associating-a-governance-group-with-a-source>).
5. Select **Create Manual Work Items** to enable the source to support additional source management features such as creating accounts and access profile management.

   > **Important**
   >
   > Once you enable this feature, it can't be disabled.

   For more information on manual work items, refer to [Work Items](<https://developer.sailpoint.com/docs/api/work-items>). For more information on SailPoint features, refer to [SailPoint Identity Services](<https://documentation.sailpoint.com/saas/help/index.html>).
6. Select **Save**.

## Connection Settings

Configure a secured, direct connection to the source.

1. Enter the Infobip host URL as **Base URL**. For example, `https://$hostname$.api.infobip.com/people/2`.
2. Enter the **API Token**.
3. Select **Save**.

## Review and Test

Perform a test to confirm the connection to SailPoint.

1. Go to **Review and Test**.
2. Confirm that the entries in each field are correct.

   If you note any mistakes, return to the section and make corrections.
3. Select **Test Connection**.

## SailPoint Application Onboarding

SailPoint application onboarding enables you to easily onboard new applications and create sources following the successful onboarding of a discovery source. To use this feature, continue to **Discovered Applications** in the SailPoint user interface.

For more information, refer to [Application Onboarding](<https://documentation.sailpoint.com/saas/help/ai/app_onboarding/index.html>) in the SailPoint SaaS documentation.

# Integrating SailPoint with Infobip

Infobip is a global, cloud-based customer engagement platform (CPaaS) for organizations that need to communicate with their customers across multiple channels without managing their own messaging infrastructure. It combines omnichannel messaging (SMS, WhatsApp, Voice, Email, and more), a customer data platform (People) for managing person and company profiles, contact center tools, and marketing automation into a single unified system, giving businesses real-time visibility into customer interactions and engagement across every channel; all built on Infobip's own global infrastructure. This document provides instructions to configure a new direct connection to an Infobip source.

> [!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 Infobip connector supports the following:

### Account Management

- Aggregate Account (Persons)

### Entitlement Management

- Aggregate Group (Companies)

> [!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. Log in to [Infobip](<https://portal.infobip.com>) with an account that has API access.
2. On the portal home page, go to **Developer Tools \> API Keys**.
3. Select **Create API key**.
4. Choose an appropriate **Expiration Date**. The API key is not valid after the selected date.
5. Select all scopes under **General** to grant read access to the API key. You can also select other scopes for further read/write operations, but you must select at least the General scope.
6. Select **Create** to create the API key. Copy the key immediately, as it is shown only once.
7. Copy and securely store the following details, which are required during connector configuration:

   - **API Base URL**
   - **API Key**

> [!NOTE]
>
> - API keys are tied to the Infobip account that generated them. Deactivating that account or revoking the key immediately invalidates it.
> - Transmit API keys only over HTTPS and store them securely.
> - Infobip authenticates API requests using the HTTP Authorization header in the format: `Authorization: App <API_KEY>` (API Key authentication).
> - OAuth 2.0 is also supported for Exchange apps, but API Key authentication is the standard method for direct API integrations.
> - Rotating or regenerating an API key invalidates the previous key.

For more information about Infobip API authentication, refer to the [Infobip API documentation](<https://www.infobip.com/docs/api/>).

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

## Required Permissions

- **Account Owner** - Full access, including account settings, billing, and API key management. Account Owners can generate API keys and grant scopes for all People data.
- **Users with People module access** - Can be granted access to view and manage Persons and Companies in the web interface. API keys generated under such a user inherit the same visibility.
- API keys inherit the permissions and scopes assigned at creation time. A key scoped only for People (read) can aggregate Persons and Companies but cannot modify messaging, contact center, or other unrelated resources.
- If a key's assigned scopes do not include People read access, calls to the Persons and Companies endpoints fail with an authorization error, even if the account itself has access in the web interface.

# Schema Reference

The application schema is used to configure the objects returned from a connector.

> [!NOTE]
>
> - The **Account Schema** tab is used to define the attributes for each object type in the application being configured. The schema attributes can be defined as **Entitlement** or **Multi-Valued**. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.
> - The schema attributes that are not present by [default](<#default-account-schema>) must be defined as strings if not specified.

The Infobip connector uses the following default correlation and object configurations.

## Default Account Schema

Each source supports a variety of details, or attributes, about each user who has an account, such as their name, email address, manager name, and location.

The set of account attributes each source stores and how they're organized is known as the account's *schema*. To best represent your data, you can configure sources to use an account schema matching the one you use in the external connector. Refer to [Managing Source Account Schemas](<https://documentation.sailpoint.com/saas/help/accounts/schema.html>) for more information.

### Default Account ID

SailPoint requires that certain attributes remain in your configuration. These attributes are referred to as *account IDs*.

> [!CAUTION]
>
> Changing the attribute marked as the account ID after aggregating accounts can result in duplicate accounts being created. To avoid this, either reset the accounts on this source before editing the account ID attribute or edit the account ID attribute before aggregating accounts.
>
> To resolve issues caused by changing account IDs, reconfigure them to their default values.

The following table lists the default account IDs for this connector:

| Account ID | Schema Object Type |
| --- | --- |
| id | Account |

### Default Account Attributes

The Infobip connector supports the following default account schema attributes and customer configurable attributes. The attributes must be defined as strings if not specified.

| Attribute Name | Description |
| --- | --- |
| id | Unique identifier for the person |
| firstName | First name of the person |
| lastName | Last name of the person |
| type | Profile type reflecting the person's status in the customer journey - LEAD or CUSTOMER. Defaults to CUSTOMER if not specified when the profile is created |
| origin | Source through which the person profile was originally created (for example, PORTAL, API, or an integrated channel) |
| modifiedFrom | Source from which the profile was last modified (for example, PORTAL, API) |
| createdAt | Timestamp when the person profile was created |
| modifiedAt | Timestamp when the person profile was last modified |
| tags | List of labels assigned to the person profile, used for filtering |
| contactInformation.email | List of email addresses associated with the person, each with an address and an isPrimary flag |
| contactInformation.phone | List of phone numbers associated with the person, each with a number and an isPrimary flag |
| companyId | Identifier of the Company (role) the associated with the person, used to link a person account to its company |

## Default Entitlement Attributes

Entitlement attributes define the entitlements, such as groups or roles, that can be assigned to the managed system's user accounts. Refer to [Managing Entitlements](<https://documentation.sailpoint.com/saas/help/access/entitlements.html>) for more information.

> [!CAUTION]
>
> Changing the attribute marked as the Entitlement ID after aggregating accounts or entitlements can result in duplicate entitlements being created, or access profiles and roles breaking. To avoid this, edit the entitlement schema before performing any aggregations.

### Default Group Attributes

The Infobip connector also supports groups. The following attributes must be configured on the managed system and in the SailPoint source schema to manage groups.

| Attribute Name | Description |
| --- | --- |
| id | Unique identifier for the company, used as the entitlement ID |
| name | Display name of the company, used as entitlement name |
| domains | List of web domains associated with the company |
| origin | Source through which the company profile was originally created (for example, PORTAL, API) |
| modifiedFrom | Source from which the company profile was last modified |
| createdAt | Timestamp when the company profile was created |
| modifiedAt | Timestamp when the company profile was last modified |