sailpoint-api-client 1.6.4 → 1.6.6

package/dist/v3/api.d.ts

@@ -172,7 +172,7 @@ export interface AccessCriteria {
  */
 export interface AccessCriteriaCriteriaListInner {
     /**
-     * Type of the propery to which this reference applies to
+     * Type of the property to which this reference applies to
      * @type {string}
      * @memberof AccessCriteriaCriteriaListInner
      */
@@ -194,6 +194,48 @@ export declare const AccessCriteriaCriteriaListInnerTypeV3: {
     readonly Entitlement: "ENTITLEMENT";
 };
 export type AccessCriteriaCriteriaListInnerTypeV3 = typeof AccessCriteriaCriteriaListInnerTypeV3[keyof typeof AccessCriteriaCriteriaListInnerTypeV3];
+/**
+ *
+ * @export
+ * @interface AccessCriteriaRequest
+ */
+export interface AccessCriteriaRequest {
+    /**
+     * Business name for the access construct list
+     * @type {string}
+     * @memberof AccessCriteriaRequest
+     */
+    'name'?: string;
+    /**
+     * List of criteria. There is a min of 1 and max of 50 items in the list.
+     * @type {Array<AccessCriteriaRequestCriteriaListInner>}
+     * @memberof AccessCriteriaRequest
+     */
+    'criteriaList'?: Array<AccessCriteriaRequestCriteriaListInner>;
+}
+/**
+ *
+ * @export
+ * @interface AccessCriteriaRequestCriteriaListInner
+ */
+export interface AccessCriteriaRequestCriteriaListInner {
+    /**
+     * Type of the property to which this reference applies to
+     * @type {string}
+     * @memberof AccessCriteriaRequestCriteriaListInner
+     */
+    'type'?: AccessCriteriaRequestCriteriaListInnerTypeV3;
+    /**
+     * ID of the object to which this reference applies to
+     * @type {string}
+     * @memberof AccessCriteriaRequestCriteriaListInner
+     */
+    'id'?: string;
+}
+export declare const AccessCriteriaRequestCriteriaListInnerTypeV3: {
+    readonly Entitlement: "ENTITLEMENT";
+};
+export type AccessCriteriaRequestCriteriaListInnerTypeV3 = typeof AccessCriteriaRequestCriteriaListInnerTypeV3[keyof typeof AccessCriteriaRequestCriteriaListInnerTypeV3];
 /**
  * Identity the access item is requested for.
  * @export
@@ -4817,7 +4859,6 @@ export interface CampaignAllOfFilter {
 }
 export declare const CampaignAllOfFilterTypeV3: {
     readonly CampaignFilter: "CAMPAIGN_FILTER";
-    readonly Rule: "RULE";
 };
 export type CampaignAllOfFilterTypeV3 = typeof CampaignAllOfFilterTypeV3[keyof typeof CampaignAllOfFilterTypeV3];
 /**
@@ -6294,6 +6335,25 @@ export interface ConflictingAccessCriteria {
      */
     'rightCriteria'?: AccessCriteria;
 }
+/**
+ *
+ * @export
+ * @interface ConflictingAccessCriteriaRequest
+ */
+export interface ConflictingAccessCriteriaRequest {
+    /**
+     *
+     * @type {AccessCriteriaRequest}
+     * @memberof ConflictingAccessCriteriaRequest
+     */
+    'leftCriteria'?: AccessCriteriaRequest;
+    /**
+     *
+     * @type {AccessCriteriaRequest}
+     * @memberof ConflictingAccessCriteriaRequest
+     */
+    'rightCriteria'?: AccessCriteriaRequest;
+}
 /**
  *
  * @export
@@ -20911,12 +20971,6 @@ export interface SodPolicy {
      * @memberof SodPolicy
      */
     'type'?: SodPolicyTypeV3;
-    /**
-     *
-     * @type {SodPolicyConflictingAccessCriteria}
-     * @memberof SodPolicy
-     */
-    'conflictingAccessCriteria'?: SodPolicyConflictingAccessCriteria;
 }
 export declare const SodPolicyStateV3: {
     readonly Enforced: "ENFORCED";
@@ -20928,25 +20982,6 @@ export declare const SodPolicyTypeV3: {
     readonly ConflictingAccessBased: "CONFLICTING_ACCESS_BASED";
 };
 export type SodPolicyTypeV3 = typeof SodPolicyTypeV3[keyof typeof SodPolicyTypeV3];
-/**
- *
- * @export
- * @interface SodPolicyConflictingAccessCriteria
- */
-export interface SodPolicyConflictingAccessCriteria {
-    /**
-     *
-     * @type {AccessCriteria}
-     * @memberof SodPolicyConflictingAccessCriteria
-     */
-    'leftCriteria'?: AccessCriteria;
-    /**
-     *
-     * @type {AccessCriteria}
-     * @memberof SodPolicyConflictingAccessCriteria
-     */
-    'rightCriteria'?: AccessCriteria;
-}
 /**
  * SOD policy.
  * @export
@@ -21006,6 +21041,294 @@ export declare const SodPolicyOwnerRefTypeV3: {
     readonly GovernanceGroup: "GOVERNANCE_GROUP";
 };
 export type SodPolicyOwnerRefTypeV3 = typeof SodPolicyOwnerRefTypeV3[keyof typeof SodPolicyOwnerRefTypeV3];
+/**
+ *
+ * @export
+ * @interface SodPolicyRead
+ */
+export interface SodPolicyRead {
+    /**
+     * Policy id
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'id'?: string;
+    /**
+     * Policy Business Name
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'name'?: string;
+    /**
+     * The time when this SOD policy is created.
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'created'?: string;
+    /**
+     * The time when this SOD policy is modified.
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'modified'?: string;
+    /**
+     * Optional description of the SOD policy
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'description'?: string | null;
+    /**
+     *
+     * @type {SodPolicyOwnerRef}
+     * @memberof SodPolicyRead
+     */
+    'ownerRef'?: SodPolicyOwnerRef;
+    /**
+     * Optional External Policy Reference
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'externalPolicyReference'?: string | null;
+    /**
+     * Search query of the SOD policy
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'policyQuery'?: string;
+    /**
+     * Optional compensating controls(Mitigating Controls)
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'compensatingControls'?: string | null;
+    /**
+     * Optional correction advice
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'correctionAdvice'?: string | null;
+    /**
+     * whether the policy is enforced or not
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'state'?: SodPolicyReadStateV3;
+    /**
+     * tags for this policy object
+     * @type {Array<string>}
+     * @memberof SodPolicyRead
+     */
+    'tags'?: Array<string>;
+    /**
+     * Policy\'s creator ID
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'creatorId'?: string;
+    /**
+     * Policy\'s modifier ID
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'modifierId'?: string | null;
+    /**
+     *
+     * @type {ViolationOwnerAssignmentConfig}
+     * @memberof SodPolicyRead
+     */
+    'violationOwnerAssignmentConfig'?: ViolationOwnerAssignmentConfig;
+    /**
+     * defines whether a policy has been scheduled or not
+     * @type {boolean}
+     * @memberof SodPolicyRead
+     */
+    'scheduled'?: boolean;
+    /**
+     * whether a policy is query based or conflicting access based
+     * @type {string}
+     * @memberof SodPolicyRead
+     */
+    'type'?: SodPolicyReadTypeV3;
+    /**
+     *
+     * @type {SodPolicyReadAllOfConflictingAccessCriteria}
+     * @memberof SodPolicyRead
+     */
+    'conflictingAccessCriteria'?: SodPolicyReadAllOfConflictingAccessCriteria;
+}
+export declare const SodPolicyReadStateV3: {
+    readonly Enforced: "ENFORCED";
+    readonly NotEnforced: "NOT_ENFORCED";
+};
+export type SodPolicyReadStateV3 = typeof SodPolicyReadStateV3[keyof typeof SodPolicyReadStateV3];
+export declare const SodPolicyReadTypeV3: {
+    readonly General: "GENERAL";
+    readonly ConflictingAccessBased: "CONFLICTING_ACCESS_BASED";
+};
+export type SodPolicyReadTypeV3 = typeof SodPolicyReadTypeV3[keyof typeof SodPolicyReadTypeV3];
+/**
+ *
+ * @export
+ * @interface SodPolicyReadAllOfConflictingAccessCriteria
+ */
+export interface SodPolicyReadAllOfConflictingAccessCriteria {
+    /**
+     *
+     * @type {AccessCriteria}
+     * @memberof SodPolicyReadAllOfConflictingAccessCriteria
+     */
+    'leftCriteria'?: AccessCriteria;
+    /**
+     *
+     * @type {AccessCriteria}
+     * @memberof SodPolicyReadAllOfConflictingAccessCriteria
+     */
+    'rightCriteria'?: AccessCriteria;
+}
+/**
+ *
+ * @export
+ * @interface SodPolicyRequest
+ */
+export interface SodPolicyRequest {
+    /**
+     * Policy id
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'id'?: string;
+    /**
+     * Policy Business Name
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'name'?: string;
+    /**
+     * The time when this SOD policy is created.
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'created'?: string;
+    /**
+     * The time when this SOD policy is modified.
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'modified'?: string;
+    /**
+     * Optional description of the SOD policy
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'description'?: string | null;
+    /**
+     *
+     * @type {SodPolicyOwnerRef}
+     * @memberof SodPolicyRequest
+     */
+    'ownerRef'?: SodPolicyOwnerRef;
+    /**
+     * Optional External Policy Reference
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'externalPolicyReference'?: string | null;
+    /**
+     * Search query of the SOD policy
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'policyQuery'?: string;
+    /**
+     * Optional compensating controls(Mitigating Controls)
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'compensatingControls'?: string | null;
+    /**
+     * Optional correction advice
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'correctionAdvice'?: string | null;
+    /**
+     * whether the policy is enforced or not
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'state'?: SodPolicyRequestStateV3;
+    /**
+     * tags for this policy object
+     * @type {Array<string>}
+     * @memberof SodPolicyRequest
+     */
+    'tags'?: Array<string>;
+    /**
+     * Policy\'s creator ID
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'creatorId'?: string;
+    /**
+     * Policy\'s modifier ID
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'modifierId'?: string | null;
+    /**
+     *
+     * @type {ViolationOwnerAssignmentConfig}
+     * @memberof SodPolicyRequest
+     */
+    'violationOwnerAssignmentConfig'?: ViolationOwnerAssignmentConfig;
+    /**
+     * defines whether a policy has been scheduled or not
+     * @type {boolean}
+     * @memberof SodPolicyRequest
+     */
+    'scheduled'?: boolean;
+    /**
+     * whether a policy is query based or conflicting access based
+     * @type {string}
+     * @memberof SodPolicyRequest
+     */
+    'type'?: SodPolicyRequestTypeV3;
+    /**
+     *
+     * @type {SodPolicyRequestAllOfConflictingAccessCriteria}
+     * @memberof SodPolicyRequest
+     */
+    'conflictingAccessCriteria'?: SodPolicyRequestAllOfConflictingAccessCriteria;
+}
+export declare const SodPolicyRequestStateV3: {
+    readonly Enforced: "ENFORCED";
+    readonly NotEnforced: "NOT_ENFORCED";
+};
+export type SodPolicyRequestStateV3 = typeof SodPolicyRequestStateV3[keyof typeof SodPolicyRequestStateV3];
+export declare const SodPolicyRequestTypeV3: {
+    readonly General: "GENERAL";
+    readonly ConflictingAccessBased: "CONFLICTING_ACCESS_BASED";
+};
+export type SodPolicyRequestTypeV3 = typeof SodPolicyRequestTypeV3[keyof typeof SodPolicyRequestTypeV3];
+/**
+ *
+ * @export
+ * @interface SodPolicyRequestAllOfConflictingAccessCriteria
+ */
+export interface SodPolicyRequestAllOfConflictingAccessCriteria {
+    /**
+     *
+     * @type {AccessCriteriaRequest}
+     * @memberof SodPolicyRequestAllOfConflictingAccessCriteria
+     */
+    'leftCriteria'?: AccessCriteriaRequest;
+    /**
+     *
+     * @type {AccessCriteriaRequest}
+     * @memberof SodPolicyRequestAllOfConflictingAccessCriteria
+     */
+    'rightCriteria'?: AccessCriteriaRequest;
+}
 /**
  *
  * @export
@@ -25427,7 +25750,7 @@ export declare const AccessRequestsApiAxiosParamCreator: (configuration?: Config
      */
     cancelAccessRequest: (cancelAccessRequest: CancelAccessRequest, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  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 doesn\'t 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\'s 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. * While requesting entitlements, maximum of 25 entitlements and 10 recipients are allowed in a request. * 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.   __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 doesn\'t 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\'s 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 {AccessRequest} accessRequest
      * @param {*} [axiosOptions] Override http request option.
@@ -25451,7 +25774,7 @@ export declare const AccessRequestsApiAxiosParamCreator: (configuration?: Config
      * @param {boolean} [count] If this is true, the *X-Total-Count* response header populates with the number of results that would be returned if limit and offset were ignored.
      * @param {number} [limit] Max number of results to return.
      * @param {number} [offset] Offset into the full result set. Usually specified with *limit* to paginate through the results. Defaults to 0 if not specified.
-     * @param {string} [filters] Filter results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#filtering-results)  Filtering is supported for the following fields and operators:  **accessRequestId**: *in*  **accountActivityItemId**: *eq, in, ge, gt, le, lt, ne, isnull, sw*  **created**: *eq, in, ge, gt, le, lt, ne, isnull, sw*
+     * @param {string} [filters] Filter results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#filtering-results)  Filtering is supported for the following fields and operators:  **accessRequestId**: *eq, in, ge, gt, le, lt, ne, sw*  **accountActivityItemId**: *eq, in, ge, gt, le, lt, ne, isnull, sw*  **created**: *eq, in, ge, gt, le, lt, ne, isnull, sw*
      * @param {string} [sorters] Sort results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#sorting-results)  Sorting is supported for the following fields: **created, modified, accountActivityItemId, name**
      * @param {string} [requestState] Filter the results by the state of the request. The only valid value is *EXECUTING*.
      * @param {*} [axiosOptions] Override http request option.
@@ -25481,7 +25804,7 @@ export declare const AccessRequestsApiFp: (configuration?: Configuration) => {
      */
     cancelAccessRequest(cancelAccessRequest: CancelAccessRequest, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
     /**
-     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  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 doesn\'t 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\'s 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. * While requesting entitlements, maximum of 25 entitlements and 10 recipients are allowed in a request. * 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.   __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 doesn\'t 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\'s 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 {AccessRequest} accessRequest
      * @param {*} [axiosOptions] Override http request option.
@@ -25505,7 +25828,7 @@ export declare const AccessRequestsApiFp: (configuration?: Configuration) => {
      * @param {boolean} [count] If this is true, the *X-Total-Count* response header populates with the number of results that would be returned if limit and offset were ignored.
      * @param {number} [limit] Max number of results to return.
      * @param {number} [offset] Offset into the full result set. Usually specified with *limit* to paginate through the results. Defaults to 0 if not specified.
-     * @param {string} [filters] Filter results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#filtering-results)  Filtering is supported for the following fields and operators:  **accessRequestId**: *in*  **accountActivityItemId**: *eq, in, ge, gt, le, lt, ne, isnull, sw*  **created**: *eq, in, ge, gt, le, lt, ne, isnull, sw*
+     * @param {string} [filters] Filter results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#filtering-results)  Filtering is supported for the following fields and operators:  **accessRequestId**: *eq, in, ge, gt, le, lt, ne, sw*  **accountActivityItemId**: *eq, in, ge, gt, le, lt, ne, isnull, sw*  **created**: *eq, in, ge, gt, le, lt, ne, isnull, sw*
      * @param {string} [sorters] Sort results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#sorting-results)  Sorting is supported for the following fields: **created, modified, accountActivityItemId, name**
      * @param {string} [requestState] Filter the results by the state of the request. The only valid value is *EXECUTING*.
      * @param {*} [axiosOptions] Override http request option.
@@ -25535,7 +25858,7 @@ export declare const AccessRequestsApiFactory: (configuration?: Configuration, b
      */
     cancelAccessRequest(requestParameters: AccessRequestsApiCancelAccessRequestRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<object>;
     /**
-     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  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 doesn\'t 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\'s 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. * While requesting entitlements, maximum of 25 entitlements and 10 recipients are allowed in a request. * 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.   __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 doesn\'t 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\'s 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 {AccessRequestsApiCreateAccessRequestRequest} requestParameters Request parameters.
      * @param {*} [axiosOptions] Override http request option.
@@ -25641,7 +25964,7 @@ export interface AccessRequestsApiListAccessRequestStatusRequest {
      */
     readonly offset?: number;
     /**
-     * Filter results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#filtering-results)  Filtering is supported for the following fields and operators:  **accessRequestId**: *in*  **accountActivityItemId**: *eq, in, ge, gt, le, lt, ne, isnull, sw*  **created**: *eq, in, ge, gt, le, lt, ne, isnull, sw*
+     * Filter results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#filtering-results)  Filtering is supported for the following fields and operators:  **accessRequestId**: *eq, in, ge, gt, le, lt, ne, sw*  **accountActivityItemId**: *eq, in, ge, gt, le, lt, ne, isnull, sw*  **created**: *eq, in, ge, gt, le, lt, ne, isnull, sw*
      * @type {string}
      * @memberof AccessRequestsApiListAccessRequestStatus
      */
@@ -25689,7 +26012,7 @@ export declare class AccessRequestsApi extends BaseAPI {
      */
     cancelAccessRequest(requestParameters: AccessRequestsApiCancelAccessRequestRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<object, any>>;
     /**
-     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  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 doesn\'t 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\'s 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. * While requesting entitlements, maximum of 25 entitlements and 10 recipients are allowed in a request. * 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.   __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 doesn\'t 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\'s 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 {AccessRequestsApiCreateAccessRequestRequest} requestParameters Request parameters.
      * @param {*} [axiosOptions] Override http request option.
@@ -38126,11 +38449,11 @@ export declare const SODPoliciesApiAxiosParamCreator: (configuration?: Configura
     /**
      * This creates both General and Conflicting Access Based policy, with a limit of 50 entitlements for each (left & right) criteria for Conflicting Access Based SOD policy. Requires role of ORG_ADMIN.
      * @summary Create sod policy
-     * @param {SodPolicy} sodPolicy
+     * @param {SodPolicyRequest} sodPolicyRequest
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    createSodPolicy: (sodPolicy: SodPolicy, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    createSodPolicy: (sodPolicyRequest: SodPolicyRequest, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * This deletes a specified SOD policy. Requires role of ORG_ADMIN.
      * @summary Delete sod policy by id
@@ -38238,11 +38561,11 @@ export declare const SODPoliciesApiAxiosParamCreator: (configuration?: Configura
      * This updates a specified SOD policy. Requires role of ORG_ADMIN.
      * @summary Update sod policy by id
      * @param {string} id The ID of the SOD policy to update.
-     * @param {SodPolicy} sodPolicy
+     * @param {SodPolicyRead} sodPolicyRead
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    putSodPolicy: (id: string, sodPolicy: SodPolicy, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    putSodPolicy: (id: string, sodPolicyRead: SodPolicyRead, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * Runs the scheduled report for the policy retrieved by passed policy ID.  The report schedule is fetched from the policy retrieved by ID.
      * @summary Evaluate one policy by id
@@ -38276,11 +38599,11 @@ export declare const SODPoliciesApiFp: (configuration?: Configuration) => {
     /**
      * This creates both General and Conflicting Access Based policy, with a limit of 50 entitlements for each (left & right) criteria for Conflicting Access Based SOD policy. Requires role of ORG_ADMIN.
      * @summary Create sod policy
-     * @param {SodPolicy} sodPolicy
+     * @param {SodPolicyRequest} sodPolicyRequest
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    createSodPolicy(sodPolicy: SodPolicy, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SodPolicy>>;
+    createSodPolicy(sodPolicyRequest: SodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SodPolicyRead>>;
     /**
      * This deletes a specified SOD policy. Requires role of ORG_ADMIN.
      * @summary Delete sod policy by id
@@ -38329,7 +38652,7 @@ export declare const SODPoliciesApiFp: (configuration?: Configuration) => {
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    getSodPolicy(id: string, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SodPolicy>>;
+    getSodPolicy(id: string, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SodPolicyRead>>;
     /**
      * This endpoint gets a specified SOD policy\'s schedule.
      * @summary Get sod policy schedule
@@ -38365,7 +38688,7 @@ export declare const SODPoliciesApiFp: (configuration?: Configuration) => {
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    listSodPolicies(limit?: number, offset?: number, count?: boolean, filters?: string, sorters?: string, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<SodPolicy>>>;
+    listSodPolicies(limit?: number, offset?: number, count?: boolean, filters?: string, sorters?: string, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<SodPolicyRead>>>;
     /**
      * Allows updating SOD Policy fields other than [\"id\",\"created\",\"creatorId\",\"policyQuery\",\"type\"] using the [JSON Patch](https://tools.ietf.org/html/rfc6902) standard. Requires role of ORG_ADMIN. This endpoint can only patch CONFLICTING_ACCESS_BASED type policies. Do not use this endpoint to patch general policies - doing so will build an API exception.
      * @summary Patch sod policy by id
@@ -38374,7 +38697,7 @@ export declare const SODPoliciesApiFp: (configuration?: Configuration) => {
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchSodPolicy(id: string, jsonPatchOperation: Array<JsonPatchOperation>, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SodPolicy>>;
+    patchSodPolicy(id: string, jsonPatchOperation: Array<JsonPatchOperation>, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SodPolicyRead>>;
     /**
      * This updates schedule for a specified SOD policy.
      * @summary Update sod policy schedule
@@ -38388,11 +38711,11 @@ export declare const SODPoliciesApiFp: (configuration?: Configuration) => {
      * This updates a specified SOD policy. Requires role of ORG_ADMIN.
      * @summary Update sod policy by id
      * @param {string} id The ID of the SOD policy to update.
-     * @param {SodPolicy} sodPolicy
+     * @param {SodPolicyRead} sodPolicyRead
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    putSodPolicy(id: string, sodPolicy: SodPolicy, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SodPolicy>>;
+    putSodPolicy(id: string, sodPolicyRead: SodPolicyRead, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<SodPolicyRead>>;
     /**
      * Runs the scheduled report for the policy retrieved by passed policy ID.  The report schedule is fetched from the policy retrieved by ID.
      * @summary Evaluate one policy by id
@@ -38430,7 +38753,7 @@ export declare const SODPoliciesApiFactory: (configuration?: Configuration, base
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    createSodPolicy(requestParameters: SODPoliciesApiCreateSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<SodPolicy>;
+    createSodPolicy(requestParameters: SODPoliciesApiCreateSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<SodPolicyRead>;
     /**
      * This deletes a specified SOD policy. Requires role of ORG_ADMIN.
      * @summary Delete sod policy by id
@@ -38477,7 +38800,7 @@ export declare const SODPoliciesApiFactory: (configuration?: Configuration, base
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    getSodPolicy(requestParameters: SODPoliciesApiGetSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<SodPolicy>;
+    getSodPolicy(requestParameters: SODPoliciesApiGetSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<SodPolicyRead>;
     /**
      * This endpoint gets a specified SOD policy\'s schedule.
      * @summary Get sod policy schedule
@@ -38509,7 +38832,7 @@ export declare const SODPoliciesApiFactory: (configuration?: Configuration, base
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    listSodPolicies(requestParameters?: SODPoliciesApiListSodPoliciesRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<Array<SodPolicy>>;
+    listSodPolicies(requestParameters?: SODPoliciesApiListSodPoliciesRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<Array<SodPolicyRead>>;
     /**
      * Allows updating SOD Policy fields other than [\"id\",\"created\",\"creatorId\",\"policyQuery\",\"type\"] using the [JSON Patch](https://tools.ietf.org/html/rfc6902) standard. Requires role of ORG_ADMIN. This endpoint can only patch CONFLICTING_ACCESS_BASED type policies. Do not use this endpoint to patch general policies - doing so will build an API exception.
      * @summary Patch sod policy by id
@@ -38517,7 +38840,7 @@ export declare const SODPoliciesApiFactory: (configuration?: Configuration, base
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchSodPolicy(requestParameters: SODPoliciesApiPatchSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<SodPolicy>;
+    patchSodPolicy(requestParameters: SODPoliciesApiPatchSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<SodPolicyRead>;
     /**
      * This updates schedule for a specified SOD policy.
      * @summary Update sod policy schedule
@@ -38533,7 +38856,7 @@ export declare const SODPoliciesApiFactory: (configuration?: Configuration, base
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    putSodPolicy(requestParameters: SODPoliciesApiPutSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<SodPolicy>;
+    putSodPolicy(requestParameters: SODPoliciesApiPutSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<SodPolicyRead>;
     /**
      * Runs the scheduled report for the policy retrieved by passed policy ID.  The report schedule is fetched from the policy retrieved by ID.
      * @summary Evaluate one policy by id
@@ -38567,10 +38890,10 @@ export declare const SODPoliciesApiFactory: (configuration?: Configuration, base
 export interface SODPoliciesApiCreateSodPolicyRequest {
     /**
      *
-     * @type {SodPolicy}
+     * @type {SodPolicyRequest}
      * @memberof SODPoliciesApiCreateSodPolicy
      */
-    readonly sodPolicy: SodPolicy;
+    readonly sodPolicyRequest: SodPolicyRequest;
 }
 /**
  * Request parameters for deleteSodPolicy operation in SODPoliciesApi.
@@ -38777,10 +39100,10 @@ export interface SODPoliciesApiPutSodPolicyRequest {
     readonly id: string;
     /**
      *
-     * @type {SodPolicy}
+     * @type {SodPolicyRead}
      * @memberof SODPoliciesApiPutSodPolicy
      */
-    readonly sodPolicy: SodPolicy;
+    readonly sodPolicyRead: SodPolicyRead;
 }
 /**
  * Request parameters for startEvaluateSodPolicy operation in SODPoliciesApi.
@@ -38836,7 +39159,7 @@ export declare class SODPoliciesApi extends BaseAPI {
      * @throws {RequiredError}
      * @memberof SODPoliciesApi
      */
-    createSodPolicy(requestParameters: SODPoliciesApiCreateSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicy, any>>;
+    createSodPolicy(requestParameters: SODPoliciesApiCreateSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicyRead, any>>;
     /**
      * This deletes a specified SOD policy. Requires role of ORG_ADMIN.
      * @summary Delete sod policy by id
@@ -38889,7 +39212,7 @@ export declare class SODPoliciesApi extends BaseAPI {
      * @throws {RequiredError}
      * @memberof SODPoliciesApi
      */
-    getSodPolicy(requestParameters: SODPoliciesApiGetSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicy, any>>;
+    getSodPolicy(requestParameters: SODPoliciesApiGetSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicyRead, any>>;
     /**
      * This endpoint gets a specified SOD policy\'s schedule.
      * @summary Get sod policy schedule
@@ -38925,7 +39248,7 @@ export declare class SODPoliciesApi extends BaseAPI {
      * @throws {RequiredError}
      * @memberof SODPoliciesApi
      */
-    listSodPolicies(requestParameters?: SODPoliciesApiListSodPoliciesRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicy[], any>>;
+    listSodPolicies(requestParameters?: SODPoliciesApiListSodPoliciesRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicyRead[], any>>;
     /**
      * Allows updating SOD Policy fields other than [\"id\",\"created\",\"creatorId\",\"policyQuery\",\"type\"] using the [JSON Patch](https://tools.ietf.org/html/rfc6902) standard. Requires role of ORG_ADMIN. This endpoint can only patch CONFLICTING_ACCESS_BASED type policies. Do not use this endpoint to patch general policies - doing so will build an API exception.
      * @summary Patch sod policy by id
@@ -38934,7 +39257,7 @@ export declare class SODPoliciesApi extends BaseAPI {
      * @throws {RequiredError}
      * @memberof SODPoliciesApi
      */
-    patchSodPolicy(requestParameters: SODPoliciesApiPatchSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicy, any>>;
+    patchSodPolicy(requestParameters: SODPoliciesApiPatchSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicyRead, any>>;
     /**
      * This updates schedule for a specified SOD policy.
      * @summary Update sod policy schedule
@@ -38952,7 +39275,7 @@ export declare class SODPoliciesApi extends BaseAPI {
      * @throws {RequiredError}
      * @memberof SODPoliciesApi
      */
-    putSodPolicy(requestParameters: SODPoliciesApiPutSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicy, any>>;
+    putSodPolicy(requestParameters: SODPoliciesApiPutSodPolicyRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<SodPolicyRead, any>>;
     /**
      * Runs the scheduled report for the policy retrieved by passed policy ID.  The report schedule is fetched from the policy retrieved by ID.
      * @summary Evaluate one policy by id