Legal hold allows placing an entity under a legal hold, which prevents data deletion processes from proceeding.

Data Protection Command API​

• POST /dataprotectioncommand/api/legalholdentity/{id}
  • Creates a new legal hold for the specified entity.
  • Requires LegalHoldEdit permission.
  • Example Payload

{
    "data": {
        "reasonId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "details": "Legal investigation ongoing",
        "durationMonths": 12,
        "responsibleTeamId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "startDate": "2026-03-03T00:00:00Z"
    }
}

• PUT /dataprotectioncommand/api/legalholdentity/{id}
  • Updates an existing legal hold for the specified entity.
  • Requires LegalHoldEdit permission.
  • Example Payload

{
    "data": {
        "reasonId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
        "details": "Updated legal investigation details",
        "durationMonths": 24,
        "responsibleTeamId": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
    }
}

• POST /dataprotectioncommand/api/legalholdentity/{id}/delete
  • Removes the legal hold from the specified entity.
  • Requires LegalHoldDelete permission.
  • Example Payload

{
    "data": {
        "removalReason": "Legal investigation concluded"
    }
}

Data Protection Query API​

• GET /dataprotectionquery/api/legalholds/entity/{id}

  • Returns the legal hold record (active or expired) for the given entity, or 204 No Content if none exists.
  • Requires LegalHoldAccess permission.

• GET /dataprotectionquery/api/legalholds/entity/{id}/status

  • Returns the status (Active or Expired) of the legal hold for the given entity, or 204 No Content if none exists.
  • Requires LegalHoldAccess, EntityDataAccessAndSearch, or EntityGroupManagementAccessAndSearch permission.

• GET /dataprotectionquery/api/legalholds/active

  • Returns a paginated list of all active legal holds (expiry date in the future) for the tenant.
  • Supports paginationToken and limit (default: 100, max: 1000) query parameters.
  • Requires LegalHoldAccess permission.

• GET /dataprotectionquery/api/legalholds/expired

  • Returns a paginated list of all expired legal holds (expiry date today or in the past) for the tenant.
  • Supports paginationToken and limit (default: 100, max: 1000) query parameters.
  • Requires LegalHoldAccess permission.

New query parameter versionsLimit (optional): An integer to specify the maximum number of versions per jurisdiction. If not provided, it returns all.

Affected Endpoints​

• GET /policyquery/api/v1/requirement-set endpoint.

• pending_ingestion
• ingestion_in_progress

This applies to batch transaction status responses in the Observability API.

• GET /api/v1/batch-transactions/batches

• GET /api/v1/rules/execution?execution_id={execution_id}

• GET /api/rules/status/{execution_id}

Affected endpoints​

• GET /api/transactions/batch/status/{batch_id}

Details​

The Retrieve Batch Status endpoint response schema has been updated to remove the failed_transaction_modification_ids and progress_percentage fields.

These fields had already been deprecated and should no longer be relied upon by API consumers.

• POST /api/rules/schedule

Affected endpoints​

• GET /api/transactions/batch/status/{batch_id}

Details​

The progress_percentage field in the response schema of the Retrieve Batch Status endpoint is now deprecated. No functional changes have been made to the endpoint — the field continues to be returned in responses during the deprecation period but should no longer be relied upon by consumers.

• POST /api/v1/data-export/trigger

Request a report generation for a specific date. The API returns a trigger ID that can be used to poll for completion status.

• GET /api/v1/data-export/{trigger_id}

Retrieve the generated export report using the trigger ID from the request endpoint.

Affected endpoints​

• GET /api/transactions/batch/status/{batch_id}

Details​

The failed_transaction_modification_ids field in the response schema of the Retrieve Batch Status endpoint is now deprecated. No functional changes have been made to the endpoint — the field continues to be returned in responses during the deprecation period but should no longer be relied upon by consumers.

• GET /api/v1/batch-transactions/batch

Affected endpoints​

• GET /api/transactions/batch/validation-result/{batch_id}

Affected endpoints​

• GET /api/transactions/batch/generate-upload-url

• POST /api/rules/rerun

Affected endpoints​

• GET /api/transactions/batch/status/{batch_id}

Data deletion process queries now return additional information about which data protection regime and conditional retention rules were applied, including the regime ID, conditional retention description, and the conditions that were evaluated during offboarding.

Data Protection Query API​

• GET /dataprotectionquery/api/datadeletionprocess/{entityId}

  • Response now includes DataProtectionRegimeId, ConditionalRetentionDescription, and AppliedConditions fields.

• POST /dataprotectionquery/api/datadeletionprocess

  • Response now includes DataProtectionRegimeId, ConditionalRetentionDescription, and AppliedConditions fields.

• GET /dataprotectionquery/api/datadeletionprocess

  • Response now includes DataProtectionRegimeId, ConditionalRetentionDescription, and AppliedConditions fields.

• GET /dataprotectionquery/api/datadeletionprocess/paged

  • Response now includes DataProtectionRegimeId, ConditionalRetentionDescription, and AppliedConditions fields.

• GET /dataprotectionquery/api/datadeletionprocess/{entityId}/journey/{journeyId}

  • Response now includes DataProtectionRegimeId, ConditionalRetentionDescription, and AppliedConditions fields.

Enhanced validation rules for conditional retention periods when creating or updating data protection regimes.

Data Protection Command API​

• POST /dataprotectioncommand/api/regime

  • Updated validation for ConditionalRetentionPeriods parameter.

• PUT /dataprotectioncommand/api/regime/{id}

  • Updated validation for ConditionalRetentionPeriods parameter.

Affected Endpoints​

• POST /screeningreceptor/api/receptor

• GET /api/v1/rules/execution

The overview endpoint now returns a boolean flag indicating whether a regime has conditional retention periods configured. The detailed endpoint returns the full list of conditional retention periods with their logic engine conditions.

Data Protection Query API​

• GET /dataprotectionquery/api/regime

  • Response now includes HasConditionalRetentionPeriods flag in DataProtectionRegimeOverviewDto to indicate if conditional retention periods are configured.

• GET /dataprotectionquery/api/regime/{id}

  • Response now includes ConditionalRetentionPeriods field in DataProtectionRegimeDto with the full list of conditional retention periods and their associated logic engine conditions.

Data protection regimes can now be configured with conditional retention periods in addition to the standard data retention period.

Data Protection Command API​

• POST /dataprotectioncommand/api/regime

  • Now accepts ConditionalRetentionPeriods parameter when creating a new data protection regime.

• PUT /dataprotectioncommand/api/regime/{id}

  • Now accepts ConditionalRetentionPeriods parameter when updating an existing data protection regime.

Data Protection Query API​

• GET /dataprotectionquery/api/configuration/automatic-reonboarding/status

  • Returns Automatic Re-Onboarding Configuration Status.

• GET /dataprotectionquery/api/datadeletionprocess/{entityId}/journey/{journeyId}

  • Returns all data deletion processes for given entity and journey Id.

Data Protection Command API​

• PUT /dataprotectioncommand/api/configuration/automatic-reonboarding/{id}

  • Updates data protection configuration.

• POST /dataprotectioncommand/api/datadeletionprocess/pause

  • Pauses data deletion process for a specified entity, jurisdiction, and journey.
  • Example Payload

        "data": {
            "entityId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "journeyId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "jurisdiction": "Argentina"
        }

• POST /dataprotectioncommand/api/datadeletionprocess/unpause
  • Unpauses data deletion process for a specified entity, jurisdiction, and journey.
  • Example Payload

        "data": {
            "entityId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "journeyId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
            "jurisdiction": "Argentina"
        }

• GET /api/v1/batch-transactions/batch

• GET /api/v1/batch-transactions/batches

Fetch rule execution information either by rule IDs or by date range.

• GET /api/v1/rules/execution

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/search-entity-drafts

Affected Endpoints​

• POST /screeningcommand/api/batch
• POST /screeningcommand/api/entity
• PUT /screeningcommand/api/entity/{entityId}
• POST /screeningcommand/api/v2/configuration/provider
• PATCH /screeningcommand/api/v2/configuration/provider/{providerId}
• GET /screeningquery/api/batch/{id}
• GET /screeningquery/api/batch/journey/{journeyId}
• GET /screeningquery/api/batch/journey/{journeyId}/process/{processId}
• GET /screeningquery/api/batch/{batchId}/entity
• GET /screeningquery/api/batch/{batchId}/entity/{entityId}
• GET /screeningquery/api/entity/{entityId}
• POST /screeningquery/api/entity/getentitieslist
• GET /screeningquery/api/v3/configuration
• GET /screeningquery/api/v3/configuration/provider/{providerId}
• POST /{anyScreeningAdapter}/api/screen

Affected Endpoints​

• POST /riskquery/api/risk-assessment
• GET /riskquery/api/risk-assessment/{taskId}
• POST /riskquery/api/risk-assessment/taskResults
• POST /riskquery/api/risk-assessment/related-parties/{taskId:guid}
• GET /riskquery/api/risk-assessment/related-parties/{taskId:guid}/entity/{entityId:guid}

Affected Endpoints​

• GET /riskquery/api/risk-model
• GET /riskquery/api/risk-model/{id}
• GET /riskquery/api/risk-model/{id}/version/{versionNumber}
• POST /riskcommand/api/risk-model
• POST /riskcommand/api/risk-model/{id}
• PUT /riskcommand/api/risk-model/{id}

• POST /api/transactions/batch/generate-upload-url

Affected Endpoints​

• GET /riskquery/api/threshold-model
• GET /riskquery/api/threshold-model/{id:guid}
• GET /riskquery/api/threshold-model/{id:guid}/version/{versionNumber:int}
• POST /riskcommand/api/threshold-model
• POST /riskcommand/api/threshold-model/{id:guid}
• PUT /riskcommand/api/threshold-model/{id:guid}
• GET /riskquery/api/risk-model
• GET /riskquery/api/risk-model/{id}
• GET /riskquery/api/risk-model/{id}/version/{versionNumber}
• POST /riskcommand/api/risk-model
• POST /riskcommand/api/risk-model/{id}
• PUT /riskcommand/api/risk-model/{id}

New "LastActionedBy" property added to MatchDto. This new proporty will be used to identify who actioned the resolution of the match, i.e Screning Agent, Screening Provider or manually by user (manuallyByUser@test.com).

Affected Endpoints​

• POST /api/batch (BatchMetadataDto)
• PUT /api/batch/id/matches (MatchDto)
• GET /api/v3/batch/{batchId}/entity/\{entityId\}/match (MatchDto)

Affected endpoints​

• POST /api/transactions/batch/generate-upload-url
• GET /api/transactions/batch/status/{batch_id}
• GET /api/transactions/batch/validation-result/{batch_id}

• GET /api/transactions/batch/validation-result/{{batch-id}}

Added reject_on_invalid parameter to the generate-upload-url endpoint to allow rejecting entire batch if any transaction is invalid.

• POST /api/transactions/batch/generate-upload-url

Returns data deletion processes sorted by tenant with pagination support.

Data Protection Query API​

• POST /dataprotectionquery/api/datadeletionprocess/paged

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/get-entities-list
• POST /entitydataquery/api/v2/entity/search-entity-drafts

Affected Endpoints​

• GET /riskquery/api/risk-model
• GET /riskquery/api/risk-model/{id}
• GET /riskquery/api/risk-model/{id}/version/{versionNumber}
• POST /riskcommand/api/risk-model
• POST /riskcommand/api/risk-model/{id}
• PUT /riskcommand/api/risk-model/{id}

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/get-entities-list
• POST /entitydataquery/api/v2/entity/search-entity-drafts

• EntityPageConfig:
  • EntityPageDisplayInvestmentAccounts (optional)
  • InvestmentAccountPageConfig (mandatory if EntityPageDisplayInvestmentAccounts = true)
    • InvestmentAccountsSections (optional)
    • InvestmentAccountDataCategory (mandatory if InvestmentAccountsSections = "Data")
    • InvestmentAccountDocumentType (mandatory if InvestmentAccountsSections = "Documents")

Affected Endpoints​

• POST /api/portal-roles/createrole
• PUT /api/portal-roles/updateroledetails
• GET /api/portal-roles/portalRole/{id}
• GET /api/portal-roles/portalRoles

Affected Endpoints​

• POST /riskquery/api/risk-assessment/related-parties/{taskId:guid}

• That all the entities being returned for the batch search results to the receptor belong to the batch.
• That the match.providerId returned for the batch search results to the receptor exists in the list of the batch providers.

Also, added fields to the Screening Command API in order to support implementation of Alias Screening. For all the endpoints, entityAliases can be sent as null or an empty list if not using Alias Screening.

Affected Endpoints​

• POST /api/batch
  • Added entityAliases to CreateBatchEntityDto (within CreateBatchDto).
• POST /api/entity
  • Added entityAliases to CreateEntityDto.
  • Added entityAliases to EntityCreatedDto (response).
• PUT /api/entity/{entityId}
  • Added entityAliases to UpdateEntityDto.
• POST /screeningreceptor/api/receptor
  • Validations explained above

Affected Endpoints​

• GET /riskquery/api/risk-assessment/related-parties/{taskId:guid}/entity/{entityId:guid}

Added optional properties to role configuration

• POST /api/portal-roles/createrole - EntityPageConfig - EnableAccessLayers (optional)
• PUT /api/portal-roles/updateroledetails - EntityPageConfig - EnableAccessLayers (optional)
• GET /api/portal-roles/portalRole/{id} - EntityPageConfig - EnableAccessLayers (optional)
• GET /api/portal-roles/portalRoles - EntityPageConfig - EnableAccessLayers (optional)

Added optional properties to user endpoints

• GET /api/portal-users/getPortalUserDetails - AccessLayersConfig (optional)
• GET /api/portal-users/getPortalUserDetailsWithoutLinkedEntities - AccessLayersConfig (optional)
• PUT /api/portal-users/updateUserDetails - AccessLayersConfig (optional)

Affected Endpoints​

• POST /entitydataquery/api/v2/entity/names

• POST /api/rules/execute

• PUT /api/entity/{entityId}/draft/{id}

Copy EntityDraft Command v2 endpoints to v3.

Affected Endpoints​

• POST /screeningreceptor/api/receptor (ScreenResponseDto, OngoingScreeningGetResultsResponseDto)
• POST /{anyScreeningAdapter}/api/resolvematches (ResolveMatchesRequestDto)
• GET /screeningquery/api/batch/{id}, GET /screeningquery/api/batch/journey/{journeyId}, GET /screeningquery/api/batch/journey/{journeyId}/process/{processId} (BatchDto)

Affected Endpoints​

• POST /screeningreceptor/api/receptor

  • Added entityAliasId to ExternalIdDto. If not using AliasScreening, entityAliasId should be always set to PrimaryName (null will default to PrimaryName).
  • Renamed AliasDto to MatchDataAliasDto for aliasesList in MatchDataDto (this is not considered a breaking change as only the name of the model was changed).
  • Added externalIds and entityAliasIds to MatchDataDto and set externalId as obsolete, since it will be removed in the future. If not using AliasScreening, entityAliasId should be always set to PrimaryName (null will default to PrimaryName).

• POST /{anyScreeningAdapter}/api/screen

  • Added entityAliases to ScreenRequestEntityDto. Only needed for providers that want to support AliasScreening.
  • Added entityAliases to OverriddenBatchEntityDto. Only needed for providers that want to support AliasScreening.

• POST /{anyScreeningAdapter}/api/resolvematches

  • Added entityAliasId to ExternalIdDto (batchExternalIds and entities.externalIds). If not using AliasScreening, entityAliasId should be always set to PrimaryName (null will default to PrimaryName).
  • Added entityAliasIds to ResolveMatchesRequestEntityDto. Only needed for providers that want to support AliasScreening.
  • Added externalIds and entityAliasIds to ResolveMatchesRequestMatchDataDto and set externalId as obsolete, since it will be removed in the future. If not using AliasScreening, entityAliasId should be always set to PrimaryName (null will default to PrimaryName).

• POST /{anyScreeningAdapter}/api/ongoingscreening

  • Added entityAliasesForEnable to OngoingScreeningRequestDto. Only needed for providers that want to support AliasScreening.

• POST /{anyScreeningAdapter}/api/ongoingscreeningupdate

  • Added entityAliases to OngoingScreeningUpdateRequestDto. Only needed for providers that want to support AliasScreening.

• GET /screeningquery/api/batch/{id}, GET /screeningquery/api/batch/journey/{journeyId}, GET /screeningquery/api/batch/journey/{journeyId}/process/{processId}

  • Added entityAliases to BatchEntitySearchDto.
  • Added entityAliasId to ExternalIdDto.

• GET /screeningquery/api/batch/{batchId}/entity, GET /screeningquery/api/batch/{batchId}/entity/{entityId}

  • Added entityAliases to BatchEntityDto.
  • Added entityAliasId to ExternalIdDto.

• GET /screeningquery/api/batch/{batchId}/entity/{entityId}/match, GET /screeningquery/api/batch/{batchId}/entity/{entityId}/match/{matchId}

  • Added entityAliasIds to MatchDto.
  • Added externalIds to MatchDataDto.
  • Renamed AliasDto to MatchDataAliasDto for aliasesList in MatchDataDto (this is not considered a breaking change as only the name of the model was changed).

• GET /screeningquery/api/entity/{entityId}, POST /screeningquery/api/entity/getentitieslist

  • Added entityAliases to ScreeningEntityDto.

Affected Endpoints​

• PUT /documentmanagementcommand/api/configuration
• GET /documentmanagementcommand/api/configuration

Affected Endpoints​

• POST /screeningcommand/api/batch
• POST /screeningcommand/api/entity
• PUT /screeningcommand/api/entity/{entityId}
• POST /screeningcommand/api/v2/configuration/provider
• PATCH /screeningcommand/api/v2/configuration/provider/{providerId}
• GET /screeningquery/api/batch/{id}
• GET /screeningquery/api/batch/journey/{journeyId}
• GET /screeningquery/api/batch/journey/{journeyId}/process/{processId}
• GET /screeningquery/api/batch/{batchId}/entity
• GET /screeningquery/api/batch/{batchId}/entity/{entityId}
• GET /screeningquery/api/entity/{entityId}
• POST /screeningquery/api/entity/getentitieslist
• GET /screeningquery/api/v3/configuration
• GET /screeningquery/api/v3/configuration/provider/{providerId}
• POST /{anyScreeningAdapter}/api/screen

Affected Endpoints​

• PUT /documentmanagementcommand/api/documentrequirement/{id}

Affected Endpoints​

• PUT /documentmanagementcommand/api/configuration
• GET /documentmanagementcommand/api/configuration

• EntityPageConfig:
  • EntityPageDataReqCategory (moved from PublicConfigEditableBase)
  • ShowEntityProfilePageV2 (optional)
  • EntityPageDocumentTypes (optional)
  • ProductRequestDetailsCategory (optional)

Affected Endpoints​

• POST /api/portal-roles/createrole
• PUT /api/portal-roles/updateroledetails
• GET /api/portal-roles/portalRole/{id}
• GET /api/portal-roles/portalRoles

• POST /entitydataquery/api/entity/getEntitiesPagedList
• POST /entitydataquery/api/v2/entity/getEntitiesPagedList

Affected Endpoints​

• PUT /journeycommand/api/journey-instance/{journeyInstanceId}/abort

• PUT /entitydatacommand/api/entity/{entityId}/draft/{id}/accessLayers

Authorization Query API​

Endpoint will return the same data as V1

• GET /authorizationquery/api/v3/team

Affected Endpoints​

• PUT /journeycommand/api/configuration
• GET /journeyquery/api/configuration

• POST /webhooks/v1/webhooks

Affected Endpoints​

• GET /documentmanagementquery/api/documentmanagement/entity/{entityId}

Authorization Query API​

Endpoint will return the same data as V1

• GET /authorizationquery/api/v3/access-layer

Affected Endpoints​

• POST /policyquery/api/v2/requirement-set/fields/grouped-lookup-options

Request example - all parameters are optional:

{
  "draftRequirementSetVersionId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "targetEntity": "Client",
  "entityType": "Individual",
  "journeyLevelDataOnly": false
}

• POST /api/transactions/batch/generate-upload-url

Get status of transaction batch

• GET /api/transactions/batch/status/{batch_id}

• GET /authorizationquery/api/authorization-profile
• GET /authorizationquery/api/{id}/authorization-profile

• POST /entitydataquery/api/v2/entity/search/by-ids

Request body:

{
   "EntityIds": ["00000000-0000-0000-0000-000000000000", "00000000-0000-0000-0000-000000000000"],
   "Pager": {
    "Size": 10,
    "From": 0,
    "SortBy": "legalEntityName.keyword",
      "SortOrder": 0
   },
   "PropertyNames": ["legalEntityName", "registrationNumber", "status"],
   "OmitNameFieldsFromProps": false
}

• GET /api/v1/transactions/summary?start_date={start_date}&end_date={end_date}

Fetch event details based on modification external ids

• GET /api/v1/transactions/events?modification_external_ids={modification_external_ids}

Fetch a list of modification ids for failed requests

• GET /api/v1/transactions/failed-modifications?date={date}

• POST /entitydataquery/api/v2/entity/search/by-ids

Request body:

{
   "EntityIds": ["00000000-0000-0000-0000-000000000000", "00000000-0000-0000-0000-000000000000"],
   "Pager": {
    "Size": 10,
    "From": 0,
    "SortBy": "legalEntityName.keyword",
      "SortOrder": 0
   },
   "PropertyNames": ["legalEntityName", "registrationNumber", "status"]
}

Please refer to Notifications Event Registry for samples of the new event notifications.

Please refer to Notifications Event Registry for samples of the new event notifications.

This method returns a list of product associations for a given root entity, excluding agency associations of subtype investment manager.

• POST /associationquery/api/association/root/{EntityId}/managedProduct

Added a new endpoint to get the verified product associations without agency associations of subtype owner and investment manager.

This method returns a list of verified product associations for a given root entity, exclduing agency associations of subtype owner and investment manager.

• POST /associationquery/api/association/root/{EntityId}/product/verified

• POST /api/product/draft/journey/\{journeyId\}/list

• POST /entitydataquery/api/entity/get-conflicts-exist-journey

Request body:

{
  "journeyId": "00000000-0000-0000-0000-000000000000",
  "entityIds": ["00000000-0000-0000-0000-000000000000"]
}

• FrontOfficeConfig:
  • NotificationDisplayEntityName (optional)
  • NotificationSendCancelledJourneyEmail (optional)
  • NewRequestDetailsCategory (mandatory if FrontOfficeConfig is not provided as null)
  • ProductRequestDetailsCategory (mandatory if FrontOfficeConfig is not provided as null)

Affected Endpoints​

• POST /api/portal-roles/createrole
• PUT /api/portal-roles/updateroledetails
• GET /api/portal-roles/portalRole/{id}
• GET /api/portal-roles/portalRoles

Affected Endpoints​

• POST /journeycommand/api/launch-journey
• GET /journeyquery/api/launch-journey/{businessProcessId}

• EntityTypeDisplay
• ExternalDataConfig:
  • IsEnabled
  • ProviderId
  • SearchFieldKey
  • IsCountryRequired
  • CountrySearchFieldKey
  • DefaultCountrySearch
  • PrimarySearchResultFieldKeys
  • SecondarySearchResultFieldKeys
  • PopulateNewRequestDetails

Affected Endpoints​

• POST /api/portal-roles/createrole
• PUT /api/portal-roles/updateroledetails
• GET /api/portal-roles/portalRole/{id}
• GET /api/portal-roles/portalRoles

SelectedGroup - determines which review and approval group was selected by the user.

Affected Endpoints​

• POST /journeycommand/api/journey-schema
• POST /journeycommand/api/journey-schema/{journeySchemaId}
• PUT /journeycommand/api/journey-schema/{journeySchemaId}/version/{versionNumber}
• GET /journeyquery/api/journey-schema/{journeySchemaId}
• GET /journeyquery/api/journey-schema/{journeySchemaId}/version/{versionNumber}

Request body:

{
  "EntityIds": ["00000000-0000-0000-0000-000000000000", "00000000-0000-0000-0000-000000000000"]
}

• PUT /entitydatacommand/api/entity/{entityId}/draft/{id}/conflicts

• PUT /entitydatacommand/api/entity/{entityId}/draft/{id}/conflicts

• POST /journeyquery/api/journey-instance/linked-journeys

• POST /v1/events-by-filter-paginated - Get events within a date range

• Create & Configure Flow
• Fetch Flow Execution details
• Execute Flow via API Trigger

SelectedGroup - determines which review and approval group was selected by the user.

Affected Endpoints​

• POST /journeycommand/api/journey-schema
• POST /journeycommand/api/journey-schema/{journeySchemaId}
• PUT /journeycommand/api/journey-schema/{journeySchemaId}/version/{versionNumber}
• GET /journeyquery/api/journey-schema/{journeySchemaId}
• GET /journeyquery/api/journey-schema/{journeySchemaId}/version/{versionNumber}

• GET /authorizationquery/api/reference-data/users
• GET /authorizationquery/api/reference-data/teams
• GET /authorizationquery/api/reference-data/team/{id}
• GET /authorizationquery/api/reference-data/access-layers

• Added Association.Properties to expose custom properties in Association Records

• GET /authorizationquery/api/team**?ExcludeUsersCount=false

These fields can be used as a means for clients to send the country codes for the related country secondary identifiers (Country ISO2 or Country ISO3 Codes) to any provider directly, as an alternative to the current method requiring this to be done only through fixed country names. This is currently not yet supported for any of our out-of-the-box providers but can be used for custom providers. We are working on releasing support for RDC and WCO soon.

Affected Endpoints​

- POST `/api/batch`
- POST `/api/entity`
- PUT `/api/entity/\{entityId\}`
- GET `/api/batch/\{id\}`
- GET `/api/batch/journey/\{journeyId\}`
- GET `/api/batch/journey/\{journeyId\}/process/\{processId\}`
- GET `/api/batch/\{batchId\}/entity`
- GET `/api/batch/\{batchId\}/entity/\{entityId\}`
- GET `/api/entity/\{entityId\}`
- POST `/api/entity/getentitieslist`

• GET /authorizationquery/api/access-layer
• GET /authorizationquery/api/team

• PUT /externaloutreachcommand/api/v1/data/updateOutreachData/{journeyId}
• PUT /externaloutreachcommand/api/v2/data/updateOutreachData/{journeyId}

Authorization Query API​

Endpoint will return the same data as V1 but there will not be users property. Instead of that there will be UsersCount

• GET /authorizationquery/api/v2/access-layer

Endpoint will return the same data as V1 but there will not be users and scopes property. Instead of that there will be UsersCount

• GET /authorizationquery/api/v2/team

Retrieve a Financial Analysis report for specific version in csv format.

• GET /financialanalysisquery/api/report/set/setId:guid/version/versionId:guid

• PUT /api/journey-instance/{journeyInstanceId}/task/{taskId}/reset

Enable users to download a financial analysis report for a specific version in CSV format. Requires FinancialAnalysisReport permission.

• GET /financialanalysisquery/api/report/set/setId:guid/version/versionId:guid

Financial Analysis Command API​

• PUT /financialanalysiscommand/api/financialanalysis/setId:guid/status - Add new supported status Waived.
• PUT /financialanalysiscommand/api/financialanalysis/setId:guid/id:guid/status - Deprecate update Financial Analysis version status endpoint.
  • Use /api/financialanalysis/setId:guid/status instead.

Affected Endpoints​

• POST /policylogicengine/api/v3/engine/evaluate-all-requirements

• POST /entitydataquery/api/entity/report-pre-sign-url

Request body:

{
  "ReportType": "type"
}

Endpoints affected:

• GET {{baseDomain}}/identitymanagementquery/api/users