/v2025/sources/{sourceId}/load-entitlements imports into group aggregation path instead of alternate entitlement type for Delimited File source

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

I am testing entitlement import on a Delimited File source in ISC, and I am seeing different behavior between UI and API.

What works:

  • In the ISC UI, Import Entitlements works correctly because there is an option to select the entitlement type.
  • When I select an alternate entitlement type, such as Profiles in UI, the import works for that type.

What does not work:

  • Using the API POST /v2025/sources/{sourceId}/load-entitlements, I do not see any way to specify the entitlement type/schema to import into.
  • The request is accepted, but the created task appears to run as Cloud Group Aggregation, not as the selected alternate entitlement type aggregation.
  • Because of this, the import behaves like the default group import path instead of the alternate entitlement type.

Observed behavior:

  • If group entitlement type exists on the source, API import succeeds and data appears under group.
  • If only an alternate entitlement type such as Profiles is configured on the source, the API request is submitted successfully and a task is created, but the entitlement data does not appear under the source as expected.
  • The API response creates a task like this:
    {
    “type”: “QUARTZ”,
    “id”: “f59d20d9054a49e8b35e0ead0a018aa0”,
    “name”: “Cloud Group Aggregation - 3a68239b12ad4443ba2ab3b1460c321f”,
    “description”: “Aggregates from the specified application.”,
    “parentName”: null,
    “launcher”: “sakshi.sharma”,
    “created”: “2026-04-03T06:00:06.888+00:00”,
    “launched”: null,
    “completed”: null,
    “progress”: null,
    “completionStatus”: null,
    “messages”: ,
    “returns”: ,
    “attributes”: {}
    }
  • This makes it look like the API is still invoking the group aggregation flow even though the source is configured for a different entitlement type.

Source setup:

  • Source type: Delimited File
  • Alternate entitlement type/schema: for example, Profiles
  • UI import supports selecting the type
  • API import endpoint used: POST /v2025/sources/{sourceId}/load-entitlements
    Example business data being imported: Conceptually, the data looks like this:
    {
    “data”: [
    {
    “Entitlement Name”: “ACTIVATION Mode”,
    “Entitlement Type”: “Profiles”,
    “Entitlement Key”: “8a819b5370621cbc01708a992c0935a9”,
    “Source Id”: “fd209e7956124375b6147ea53f78cfa8”
    },
    {
    “Entitlement Name”: “RENEWAL GATEWAY”,
    “Entitlement Type”: “Profiles”,
    “Entitlement Key”: “8a819b5370621cbc01708a992cc035aa”,
    “Source Id”: “fd209e7956124375b6147ea53f78cfa8”
    }
    ]
    }

Question:

  1. Is there any supported way to specify the entitlement type/schema when calling: POST /v2025/sources/{sourceId}/load-entitlements
    For example, can the API be told to import into Profiles instead of using the default group aggregation path?
  2. If this is not supported by load-entitlements, is there any other ISC API available to upload/import entitlement data for a selected entitlement type, other than using the UI?
  3. If not, is this a current limitation of the load-entitlements API for Delimited File sources with multiple entitlement types/schemas?

Summarized context:

  • UI works because it allows selecting the entitlement type
  • API does not expose an equivalent selector
  • API-created task appears as Cloud Group Aggregation, which suggests it is not targeting the alternate entitlement type
2

This looks like a product/API gap, not a file issue. The public v2025 /sources/{sourceId}/load-entitlements API only documents source ID + CSV upload for delimited sources, and I do not see any supported parameter to choose an alternate entitlement type like Profiles.

The interesting part is that SailPoint does expose schemaName on the entitlements schema upload API, but not on the entitlement aggregation/import API. So your observation that the API falls back to Cloud Group Aggregation is consistent with what is currently documented.

So my read is:

  • No, there is no documented way to choose the entitlement type on load-entitlements
  • No, I do not see another public API that supports that selection during import
  • Yes, this currently appears to be a limitation for Delimited File sources with multiple entitlement schemas/types in the public API

I would raise this with Support / Product, because the UI and public API do not seem functionally equivalent here.