sailpoint-api-client 1.7.17 → 1.7.19

package/dist/beta/common.js

@@ -250,7 +250,7 @@ var createRequestFunction = function (axiosArgs, globalAxios, BASE_PATH, configu
         if (axios === void 0) { axios = globalAxios; }
         if (basePath === void 0) { basePath = BASE_PATH; }
         (0, axios_retry_1.default)(axios, configuration.retriesConfig);
-        var headers = __assign(__assign({ 'User-Agent': 'OpenAPI-Generator/1.7.17/ts' }, axiosArgs.axiosOptions.headers), { 'X-SailPoint-SDK': 'typescript-1.7.17' });
+        var headers = __assign(__assign({ 'User-Agent': 'OpenAPI-Generator/1.7.19/ts' }, axiosArgs.axiosOptions.headers), { 'X-SailPoint-SDK': 'typescript-1.7.19' });
         if (!configuration.experimental && ("X-SailPoint-Experimental" in headers)) {
             throw new Error("You are using Experimental APIs. Set configuration.experimental = True to enable these APIs in the SDK.");
         }

package/dist/v2024/api.d.ts

@@ -6503,6 +6503,13 @@ export interface ArgumentV2024 {
      */
     'type'?: string | null;
 }
+/**
+ *
+ * @export
+ * @interface ArrayInner1V2024
+ */
+export interface ArrayInner1V2024 {
+}
 /**
  *
  * @export
@@ -21053,6 +21060,42 @@ export interface JITConfigurationV2024 {
         [key: string]: string;
     };
 }
+/**
+ * A JSONPatch Operation for Role Mining endpoints, supporting only remove and replace operations as defined by [RFC 6902 - JSON Patch](https://tools.ietf.org/html/rfc6902)
+ * @export
+ * @interface JsonPatchOperationRoleMiningV2024
+ */
+export interface JsonPatchOperationRoleMiningV2024 {
+    /**
+     * The operation to be performed
+     * @type {string}
+     * @memberof JsonPatchOperationRoleMiningV2024
+     */
+    'op': JsonPatchOperationRoleMiningV2024OpV2024;
+    /**
+     * A string JSON Pointer representing the target path to an element to be affected by the operation
+     * @type {string}
+     * @memberof JsonPatchOperationRoleMiningV2024
+     */
+    'path': string;
+    /**
+     *
+     * @type {JsonPatchOperationRoleMiningValueV2024}
+     * @memberof JsonPatchOperationRoleMiningV2024
+     */
+    'value'?: JsonPatchOperationRoleMiningValueV2024;
+}
+export declare const JsonPatchOperationRoleMiningV2024OpV2024: {
+    readonly Remove: "remove";
+    readonly Replace: "replace";
+};
+export type JsonPatchOperationRoleMiningV2024OpV2024 = typeof JsonPatchOperationRoleMiningV2024OpV2024[keyof typeof JsonPatchOperationRoleMiningV2024OpV2024];
+/**
+ * @type JsonPatchOperationRoleMiningValueV2024
+ * The value to be used for the operation, required for \"replace\" operations
+ * @export
+ */
+export type JsonPatchOperationRoleMiningValueV2024 = Array<ArrayInner1V2024> | boolean | number | object | string;
 /**
  * A JSONPatch Operation as defined by [RFC 6902 - JSON Patch](https://tools.ietf.org/html/rfc6902)
  * @export
@@ -21079,8 +21122,12 @@ export interface JsonPatchOperationV2024 {
     'value'?: UpdateMultiHostSourcesRequestInnerValueV2024;
 }
 export declare const JsonPatchOperationV2024OpV2024: {
+    readonly Add: "add";
     readonly Remove: "remove";
     readonly Replace: "replace";
+    readonly Move: "move";
+    readonly Copy: "copy";
+    readonly Test: "test";
 };
 export type JsonPatchOperationV2024OpV2024 = typeof JsonPatchOperationV2024OpV2024[keyof typeof JsonPatchOperationV2024OpV2024];
 /**
@@ -27865,36 +27912,6 @@ export declare const PatOwnerV2024TypeV2024: {
     readonly Identity: "IDENTITY";
 };
 export type PatOwnerV2024TypeV2024 = typeof PatOwnerV2024TypeV2024[keyof typeof PatOwnerV2024TypeV2024];
-/**
- *
- * @export
- * @interface PatchPotentialRoleRequestInnerV2024
- */
-export interface PatchPotentialRoleRequestInnerV2024 {
-    /**
-     * The operation to be performed
-     * @type {string}
-     * @memberof PatchPotentialRoleRequestInnerV2024
-     */
-    'op'?: PatchPotentialRoleRequestInnerV2024OpV2024;
-    /**
-     * A string JSON Pointer representing the target path to an element to be affected by the operation
-     * @type {string}
-     * @memberof PatchPotentialRoleRequestInnerV2024
-     */
-    'path': string;
-    /**
-     *
-     * @type {UpdateMultiHostSourcesRequestInnerValueV2024}
-     * @memberof PatchPotentialRoleRequestInnerV2024
-     */
-    'value'?: UpdateMultiHostSourcesRequestInnerValueV2024;
-}
-export declare const PatchPotentialRoleRequestInnerV2024OpV2024: {
-    readonly Remove: "remove";
-    readonly Replace: "replace";
-};
-export type PatchPotentialRoleRequestInnerV2024OpV2024 = typeof PatchPotentialRoleRequestInnerV2024OpV2024[keyof typeof PatchPotentialRoleRequestInnerV2024OpV2024];
 /**
  *
  * @export
@@ -33228,7 +33245,7 @@ export interface RoleMiningIdentityDistributionDistributionInnerV2024 {
      * @type {string}
      * @memberof RoleMiningIdentityDistributionDistributionInnerV2024
      */
-    'attributeValue'?: string;
+    'attributeValue'?: string | null;
     /**
      * The number of identities that have this attribute value
      * @type {number}
@@ -33401,6 +33418,25 @@ export declare const RoleMiningPotentialRoleExportStateV2024: {
     readonly Error: "ERROR";
 };
 export type RoleMiningPotentialRoleExportStateV2024 = typeof RoleMiningPotentialRoleExportStateV2024[keyof typeof RoleMiningPotentialRoleExportStateV2024];
+/**
+ * The potential role reference
+ * @export
+ * @interface RoleMiningPotentialRolePotentialRoleRefV2024
+ */
+export interface RoleMiningPotentialRolePotentialRoleRefV2024 {
+    /**
+     * Id of the potential role
+     * @type {string}
+     * @memberof RoleMiningPotentialRolePotentialRoleRefV2024
+     */
+    'id'?: string;
+    /**
+     * Name of the potential role
+     * @type {string}
+     * @memberof RoleMiningPotentialRolePotentialRoleRefV2024
+     */
+    'name'?: string;
+}
 /**
  *
  * @export
@@ -33675,12 +33711,24 @@ export interface RoleMiningPotentialRoleV2024 {
      * @memberof RoleMiningPotentialRoleV2024
      */
     'identityIds'?: Array<string>;
+    /**
+     * The status for this identity group which can be OBTAINED or COMPRESSED
+     * @type {string}
+     * @memberof RoleMiningPotentialRoleV2024
+     */
+    'identityGroupStatus'?: string | null;
     /**
      * Name of the potential role.
      * @type {string}
      * @memberof RoleMiningPotentialRoleV2024
      */
     'name'?: string;
+    /**
+     *
+     * @type {RoleMiningPotentialRolePotentialRoleRefV2024}
+     * @memberof RoleMiningPotentialRoleV2024
+     */
+    'potentialRoleRef'?: RoleMiningPotentialRolePotentialRoleRefV2024 | null;
     /**
      *
      * @type {RoleMiningPotentialRoleProvisionStateV2024 & object}
@@ -40269,13 +40317,6 @@ export declare const SubscriptionPatchRequestInnerV2024OpV2024: {
     readonly Copy: "copy";
 };
 export type SubscriptionPatchRequestInnerV2024OpV2024 = typeof SubscriptionPatchRequestInnerV2024OpV2024[keyof typeof SubscriptionPatchRequestInnerV2024OpV2024];
-/**
- *
- * @export
- * @interface SubscriptionPatchRequestInnerValueAnyOfInnerV2024
- */
-export interface SubscriptionPatchRequestInnerValueAnyOfInnerV2024 {
-}
 /**
  * The value to be used for the operation, required for \"add\" and \"replace\" operations
  * @export
@@ -46003,7 +46044,7 @@ export declare const AccessRequestsV2024ApiAxiosParamCreator: (configuration?: C
      */
     closeAccessRequest: (closeAccessRequestV2024: CloseAccessRequestV2024, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * >**Required scopes:** ORG_ADMIN requires idn:access-request:manage. USER level requires idn:access-request-self:manage (Personal Access Token only).  Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
+     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
      * @summary Submit access request
      * @param {AccessRequestV2024} accessRequestV2024
      * @param {*} [axiosOptions] Override http request option.
@@ -46118,7 +46159,7 @@ export declare const AccessRequestsV2024ApiFp: (configuration?: Configuration) =
      */
     closeAccessRequest(closeAccessRequestV2024: CloseAccessRequestV2024, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
     /**
-     * >**Required scopes:** ORG_ADMIN requires idn:access-request:manage. USER level requires idn:access-request-self:manage (Personal Access Token only).  Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
+     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
      * @summary Submit access request
      * @param {AccessRequestV2024} accessRequestV2024
      * @param {*} [axiosOptions] Override http request option.
@@ -46233,7 +46274,7 @@ export declare const AccessRequestsV2024ApiFactory: (configuration?: Configurati
      */
     closeAccessRequest(requestParameters: AccessRequestsV2024ApiCloseAccessRequestRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<object>;
     /**
-     * >**Required scopes:** ORG_ADMIN requires idn:access-request:manage. USER level requires idn:access-request-self:manage (Personal Access Token only).  Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
+     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
      * @summary Submit access request
      * @param {AccessRequestsV2024ApiCreateAccessRequestRequest} requestParameters Request parameters.
      * @param {*} [axiosOptions] Override http request option.
@@ -46594,7 +46635,7 @@ export declare class AccessRequestsV2024Api extends BaseAPI {
      */
     closeAccessRequest(requestParameters: AccessRequestsV2024ApiCloseAccessRequestRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<object, any>>;
     /**
-     * >**Required scopes:** ORG_ADMIN requires idn:access-request:manage. USER level requires idn:access-request-self:manage (Personal Access Token only).  Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
+     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
      * @summary Submit access request
      * @param {AccessRequestsV2024ApiCreateAccessRequestRequest} requestParameters Request parameters.
      * @param {*} [axiosOptions] Override http request option.
@@ -61237,23 +61278,23 @@ export declare const IAIRoleMiningV2024ApiAxiosParamCreator: (configuration?: Co
      * @summary Update a potential role
      * @param {string} sessionId The role mining session id
      * @param {string} potentialRoleId The potential role summary id
-     * @param {Array<PatchPotentialRoleRequestInnerV2024>} patchPotentialRoleRequestInnerV2024
+     * @param {Array<JsonPatchOperationRoleMiningV2024>} jsonPatchOperationRoleMiningV2024
      * @param {string} [xSailPointExperimental] Use this header to enable this experimental API.
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchPotentialRole: (sessionId: string, potentialRoleId: string, patchPotentialRoleRequestInnerV2024: Array<PatchPotentialRoleRequestInnerV2024>, xSailPointExperimental?: string, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    patchPotentialRole: (sessionId: string, potentialRoleId: string, jsonPatchOperationRoleMiningV2024: Array<JsonPatchOperationRoleMiningV2024>, xSailPointExperimental?: string, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * The method updates an existing potential role using.  The following fields can be modified:  * `description`  * `name`  * `saved`   >**NOTE: All other fields cannot be modified.**
      * @summary Update a potential role session
      * @param {string} sessionId The role mining session id
      * @param {string} potentialRoleId The potential role summary id
-     * @param {Array<JsonPatchOperationV2024>} jsonPatchOperationV2024
+     * @param {Array<JsonPatchOperationRoleMiningV2024>} jsonPatchOperationRoleMiningV2024
      * @param {string} [xSailPointExperimental] Use this header to enable this experimental API.
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchPotentialRoleSession: (sessionId: string, potentialRoleId: string, jsonPatchOperationV2024: Array<JsonPatchOperationV2024>, xSailPointExperimental?: string, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    patchPotentialRoleSession: (sessionId: string, potentialRoleId: string, jsonPatchOperationRoleMiningV2024: Array<JsonPatchOperationRoleMiningV2024>, xSailPointExperimental?: string, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * The  method updates an existing role mining session using PATCH. Supports op in {\"replace\"} and changes to pruneThreshold and/or minNumIdentitiesInPotentialRole. The potential roles in this role mining session is then re-calculated.
      * @summary Patch a role mining session
@@ -61541,23 +61582,23 @@ export declare const IAIRoleMiningV2024ApiFp: (configuration?: Configuration) =>
      * @summary Update a potential role
      * @param {string} sessionId The role mining session id
      * @param {string} potentialRoleId The potential role summary id
-     * @param {Array<PatchPotentialRoleRequestInnerV2024>} patchPotentialRoleRequestInnerV2024
+     * @param {Array<JsonPatchOperationRoleMiningV2024>} jsonPatchOperationRoleMiningV2024
      * @param {string} [xSailPointExperimental] Use this header to enable this experimental API.
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchPotentialRole(sessionId: string, potentialRoleId: string, patchPotentialRoleRequestInnerV2024: Array<PatchPotentialRoleRequestInnerV2024>, xSailPointExperimental?: string, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
+    patchPotentialRole(sessionId: string, potentialRoleId: string, jsonPatchOperationRoleMiningV2024: Array<JsonPatchOperationRoleMiningV2024>, xSailPointExperimental?: string, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
     /**
      * The method updates an existing potential role using.  The following fields can be modified:  * `description`  * `name`  * `saved`   >**NOTE: All other fields cannot be modified.**
      * @summary Update a potential role session
      * @param {string} sessionId The role mining session id
      * @param {string} potentialRoleId The potential role summary id
-     * @param {Array<JsonPatchOperationV2024>} jsonPatchOperationV2024
+     * @param {Array<JsonPatchOperationRoleMiningV2024>} jsonPatchOperationRoleMiningV2024
      * @param {string} [xSailPointExperimental] Use this header to enable this experimental API.
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchPotentialRoleSession(sessionId: string, potentialRoleId: string, jsonPatchOperationV2024: Array<JsonPatchOperationV2024>, xSailPointExperimental?: string, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
+    patchPotentialRoleSession(sessionId: string, potentialRoleId: string, jsonPatchOperationRoleMiningV2024: Array<JsonPatchOperationRoleMiningV2024>, xSailPointExperimental?: string, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
     /**
      * The  method updates an existing role mining session using PATCH. Supports op in {\"replace\"} and changes to pruneThreshold and/or minNumIdentitiesInPotentialRole. The potential roles in this role mining session is then re-calculated.
      * @summary Patch a role mining session
@@ -62591,10 +62632,10 @@ export interface IAIRoleMiningV2024ApiPatchPotentialRoleRequest {
     readonly potentialRoleId: string;
     /**
      *
-     * @type {Array<PatchPotentialRoleRequestInnerV2024>}
+     * @type {Array<JsonPatchOperationRoleMiningV2024>}
      * @memberof IAIRoleMiningV2024ApiPatchPotentialRole
      */
-    readonly patchPotentialRoleRequestInnerV2024: Array<PatchPotentialRoleRequestInnerV2024>;
+    readonly jsonPatchOperationRoleMiningV2024: Array<JsonPatchOperationRoleMiningV2024>;
     /**
      * Use this header to enable this experimental API.
      * @type {string}
@@ -62622,10 +62663,10 @@ export interface IAIRoleMiningV2024ApiPatchPotentialRoleSessionRequest {
     readonly potentialRoleId: string;
     /**
      *
-     * @type {Array<JsonPatchOperationV2024>}
+     * @type {Array<JsonPatchOperationRoleMiningV2024>}
      * @memberof IAIRoleMiningV2024ApiPatchPotentialRoleSession
      */
-    readonly jsonPatchOperationV2024: Array<JsonPatchOperationV2024>;
+    readonly jsonPatchOperationRoleMiningV2024: Array<JsonPatchOperationRoleMiningV2024>;
     /**
      * Use this header to enable this experimental API.
      * @type {string}