generated: '2026-09-09' method: searched source: https://docs.fenergox.com/release-notes/api-changelog url: https://docs.fenergox.com/release-notes/api-changelog feeds: rss: https://docs.fenergox.com/release-notes/api-changelog/rss.xml atom: https://docs.fenergox.com/release-notes/api-changelog/atom.xml scheme: Keep-a-Changelog style categories (Added / Changed / Fixed / Deprecated / Removed) per API domain, dated, tagged by domain entry_count_in_feed: 132 earliest_in_site: '2024-09-02' latest_in_feed: '2026-08-27' related_feeds: product_release_notes: https://docs.fenergox.com/release-notes/fenergo-release-notes notices_of_change: https://docs.fenergox.com/notice-of-change transaction_monitoring_release_notes: https://docs.fenergox.com/release-notes/transaction-monitoring-release-notes portal_release_notes: https://docs.fenergox.com/release-notes/portal-release-notes salesforce_app_release_notes: https://docs.fenergox.com/release-notes/salesforce-app-release-notes note: Fenergo runs a dedicated, dated API changelog separate from its product release notes, tagged by API domain (entity-data, journey, policy, screening, risk, portal-tenant, document-management, data-protection, event-ingress, event-notifications, integration-flows, supergraph, and seven transaction-monitoring tags). Breaking removals appear explicitly, e.g. "TM Transaction Batch Upload — Deprecated batch status fields removed" (2026-03-25) and "progress_percentage field deprecated" (2026-03-20). breaking_or_deprecating_in_window: 3 entries: - date: '2026-08-27' title: Screening – Added kind: added domains: - Screening url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/27/screening/Screening-Added summary: Screening now supports uploading, reusing, and deleting documents at both the entity level and the individual match level within a batch, using the same upload-URL/reuse pattern as other document flows in the platform. New materiality endpoints let users escalate and de-escalate a materiality task on an entity, trigger aggregate entity materiality calculation for a batch, and retrieve the full mat - date: '2026-08-14' title: Entity-Data – Changed kind: changed domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/14/entity-data/Entity-Data-Changed summary: The partial-properties endpoint is now unconditionally available to all callers. Request/response schema is unchanged. - date: '2026-08-11' title: Entity-Data – Added kind: added domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/11/entity-data/Entity-Data-Added summary: New endpoint returning a page of draft entity/journey membership ({ EntityId, EntityDraftId }) per matching draft, for callers that need journey draft membership without the full draft payload. Same authorization/filtering rules as the existing search endpoint. Request gains an optional page options object (page size, pagination token, sort order); response is now a page of items plus a pagination - date: '2026-08-03' title: TM Observability – Changed kind: changed domains: - TM Observability url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/03/tm-observability/Tm-Observability-Rate-Limit-Added summary: The Observability API is now subject to a per-tenant rate limit. - date: '2026-08-03' title: TM Rule Execution – Changed kind: changed domains: - TM Rule Execution url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/03/tm-rule-execution/Tm-Rule-Execution-Rate-Limit-Added summary: The Rule Execution and Rule Execution Status APIs are now subject to per-tenant rate limits. - date: '2026-08-03' title: TM Rule Rerun – Changed kind: changed domains: - TM Rule Rerun url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/03/tm-rule-rerun/Tm-Rule-Rerun-Rate-Limit-Added summary: The Rule Rerun API is now subject to a per-tenant rate limit. - date: '2026-08-03' title: TM Rule Schedule – Changed kind: changed domains: - TM Rule Schedule url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/03/tm-rule-schedule/Tm-Rule-Schedule-Rate-Limit-Added summary: The Rule Schedule API is now subject to a per-tenant rate limit. - date: '2026-08-03' title: TM Transaction Batch Upload – Changed kind: changed domains: - TM Trx Batch Upload url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/03/tm-trx-batch-upload/Tm-Trx-Batch-Upload-Rate-Limit-Added summary: The Batch Upload API is now subject to per-tenant rate limits. - date: '2026-08-03' title: TM Transaction API – Changed kind: changed domains: - TM Trx Ingestion url: https://docs.fenergox.com/release-notes/api-changelog/2026/08/03/tm-trx-ingestion/Tm-Trx-Ingestion-Rate-Limit-Added summary: The Transaction API is now subject to a per-tenant rate limit. - date: '2026-07-29' title: Entity-Data – Changed kind: changed domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/07/29/entity-data/Entity-Data-Changed summary: The maximum number of EntityIds accepted per request is raised from 10 to 100. Requests above the new limit are still rejected with a validation error. Response shape is unchanged. - date: '2026-07-07' title: Screening – Added kind: added domains: - Screening url: https://docs.fenergox.com/release-notes/api-changelog/2026/07/07/screening/Screening-Added summary: 'New V3 Entity endpoints are now available. These replace the existing V1/V2 entity endpoints and introduce two key improvements: support for multiple addresses per entity in SearchCriteria, and per-configuration-set targeting when toggling Ongoing Screening.' - date: '2026-07-06' title: Entity-Data – Added kind: added domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/07/06/entity-data/Entity-Data-Added summary: New endpoint that returns a named subset of an entity draft's properties for up to 10 drafts in a single request. Each result carries the draft's id, type, and only the top-level property keys named in the request. Requested keys that don't exist on a draft are omitted, and drafts that don't exist or that the caller cannot access are omitted from the response. - date: '2026-07-03' title: Entity-Data – Fixed kind: fixed domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/07/03/entity-data/Entity-Data-Fixed summary: GraphQL responses — including auth-denied ones — from both EntityData subgraph hosts now include the Platform security headers Strict-Transport-Security and Content-Security-Policy. - date: '2026-06-29' title: Entity-Data – Fixed kind: fixed domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/06/29/entity-data/Entity-Data-Fixed summary: Entity draft/entity update validation now honours Policy ExternalDataGroupProvider rules for data group fields when creating external adapter validation requests. Request/response schema is unchanged; affected command endpoints now correctly reject invalid data group rows returned by the external provider. - date: '2026-06-24' title: Entity-Data – Changed kind: changed domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/06/24/entity-data/Entity-Data-Changed summary: Entity draft/entity update validation now sends data group fields to external adapter providers as grouped requests (one request per collection row per provider) instead of individual single-field requests. Request/response schema is unchanged; validation error messages returned to callers are unaffected. - date: '2026-05-29' title: Journey – Added kind: added domains: [] url: https://docs.fenergox.com/release-notes/api-changelog/2026/05/29/journey/SLA-Event-Notifications summary: 'Two new SLA Event Notifications have been added to the journey feed:' - date: '2026-05-28' title: Entity-Data – Added kind: added domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/05/28/entity-data/Entity-Data-Added summary: New endpoint that returns the entity id, draft id (when applicable), type, display name, and aggregate version for each requested entity within a journey context. Uses the journey's draft when present, falling back to the verified entity record otherwise. Only accessible records are returned; inaccessible and forbidden records are silently omitted. - date: '2026-05-20' title: Entity-Data – Changed kind: changed domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/05/20/entity-data/Entity-Data-Changed summary: The conflicts-exist check now persists a conflict-free result once a comparison finds no data conflicts, clearing the phantom conflict badge with no client-visible API change. - date: '2026-05-19' title: Entity-Data – Added kind: added domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/05/19/entity-data/Entity-Data-Added summary: 'Journey Level Data (JLD) property values are now surfaced in Advanced Reporting: entity draft properties (scalars, Data Groups, and custom properties) are projected into the reporting data store alongside regular entity draft data.' - date: '2026-05-15' title: Association – Changed kind: changed domains: - Association url: https://docs.fenergox.com/release-notes/api-changelog/2026/05/15/association/Association-Changed summary: The Agency Product Verified endpoint now accepts an optional journeyId query parameter to check whether all associations for a completed journey are verified. - date: '2026-05-06' title: Data Protection – Added kind: added domains: - Data Protection url: https://docs.fenergox.com/release-notes/api-changelog/2026/05/06/data-protection/Data-Protection-Added summary: Added new endpoints for Legal Hold management. - date: '2026-04-17' title: Policy – Changed kind: changed domains: - Policy url: https://docs.fenergox.com/release-notes/api-changelog/2026/04/17/policy/Policy-Changed summary: Extended the requirement set retrieval API to support a configurable limit on the number of versions returned per jurisdiction. - date: '2026-04-09' title: Entity-Data – Added kind: added domains: - Entity-Data url: https://docs.fenergox.com/release-notes/api-changelog/2026/04/09/entity-data/Entity-Data-Added summary: Validation error messages now use the field's friendly name (e.g. "First Name") instead of the internal datakey (e.g. firstName). - date: '2026-04-02' title: TM Observability Batch Transaction statuses - Changed kind: changed domains: - TM Observability url: https://docs.fenergox.com/release-notes/api-changelog/2026/04/02/tm-observability/TM-Observability-Batch-Statuses-Added summary: 'The batch transaction response status now includes two additional intermediate values:' - date: '2026-03-27' title: TM Observability Rule Execution Summary filtering by execution_id – Added kind: added domains: - TM Observability url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/27/tm-observability/TM-Observability-Rule-Execution-Filter-Execution-Id-Added summary: Poll the execution status summary from the Observability API using the execution_id. This works for both tenants using either the Rule Rerun API or the Rule Execution API endpoints - date: '2026-03-27' title: TM Rule Execution Status – Added kind: added domains: - TM Rule Execution url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/27/tm-rule-execution/TM-Rule-Execution-Status-Added summary: Poll the rule execution status summary using the execution_id retrieved only when using the Rule Execution API endpoint - date: '2026-03-25' title: TM Transaction Batch Upload – Deprecated batch status fields removed kind: deprecated domains: - TM Trx Batch Upload url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/25/tm-trx-batch-upload/Tm-Trx-Batch-Status-Deprecated-Fields-Removed summary: The previously deprecated failedtransactionmodificationids and progresspercentage fields are no longer returned in the batch status response. - date: '2026-03-23' title: TM Rule Schedule – Added kind: added domains: - TM Rule Schedule url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/23/tm-rule-schedule/Tm-Rule-schedule-Added summary: The Rule Schedule API provides visibility into rules execution schedule. - date: '2026-03-20' title: TM Transaction Batch Upload – progress_percentage field deprecated kind: deprecated domains: - TM Trx Batch Upload url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/20/tm-trx-batch-upload/Tm-Trx-Batch-Progress-Percentage-Field-Deprecated summary: The progress_percentage field in the batch status response has been marked as deprecated and will be removed in a future version. - date: '2026-03-18' title: TM Data Export – Added kind: added domains: - TM Observability url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/18/tm-observability/TM-Observability-Added summary: Request and retrieve data export reports for specific dates through the Transaction Monitoring Observability API. - date: '2026-03-13' title: TM Transaction Batch Upload – failed_transaction_modification_ids field deprecated kind: deprecated domains: - TM Trx Batch Upload url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/13/tm-trx-batch-upload/Tm-Trx-Batch-Status-Field-Deprecated summary: The failedtransactionmodification_ids field in the batch status response has been marked as deprecated and will be removed in a future version. - date: '2026-03-10' title: TM Observability – Changed kind: changed domains: - TM Observability url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/10/tm-observability/Tm-Observability-Changed summary: The response now includes rejectoninvalid and error message in the response for observability batch transaction API. - date: '2026-03-05' title: TM Transaction Batch Upload – Modification ID uniqueness validation updated kind: updated domains: - TM Trx Batch Upload url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/05/tm-trx-batch-upload/Tm-Trx-Batch-Duplicate-Validation-Updated summary: Transactions with non-unique modification IDs within a batch are marked accordingly in the validation results file, and those transactions are rejected. - date: '2026-03-04' title: TM Transaction Batch Upload – reject_on_invalid for batch creation updated kind: updated domains: - TM Trx Batch Upload url: https://docs.fenergox.com/release-notes/api-changelog/2026/03/04/tm-trx-batch-upload/Tm-Trx-Batch-API-update summary: rejectoninvalid configuration flag moved to request body. - date: '2026-02-23' title: TM Rule Rerun – Added kind: added domains: - TM Rule Rerun url: https://docs.fenergox.com/release-notes/api-changelog/2026/02/23/tm-rule-rerun/Tm-Rule-Rerun-Added summary: Trigger the execution of set of scheduled rules for a specific date - date: '2026-02-17' title: TM Transaction Batch Upload – Unique transaction validation within a batch kind: changed domains: - TM Trx Batch Upload url: https://docs.fenergox.com/release-notes/api-changelog/2026/02/17/tm-trx-batch-upload/Tm-Trx-Batch-Check-Duplicate-Trx summary: Each batch must contain only unique transaction modification IDs. If duplicate transaction modification IDs are detected, the entire batch will be rejected, regardless of the rejectoninvalid flag is set to either true or false. - date: '2026-02-04' title: Data Protection – Updated kind: updated domains: - Data Protection url: https://docs.fenergox.com/release-notes/api-changelog/2026/02/04/data-protection/Data-Protection-Updated summary: Added conditional retention tracking fields to DataDeletionProcessDto response. - date: '2026-01-27' title: Data Protection – Updated kind: updated domains: - Data Protection url: https://docs.fenergox.com/release-notes/api-changelog/2026/01/27/data-protection/Data-Protection-Updated summary: Updated validation for ConditionalRetentionPeriods in DataProtectionRegime. - date: '2026-01-27' title: Screening – Updated kind: updated domains: - Screening url: https://docs.fenergox.com/release-notes/api-changelog/2026/01/27/screening/Screening-Updated summary: Added validation in the receptor for the ScreenResponseDto to ensure that entities is not null. - date: '2026-01-27' title: TM Observability – Changed kind: changed domains: - TM Observability url: https://docs.fenergox.com/release-notes/api-changelog/2026/01/27/tm-observability/Tm-Observability-Changed summary: The response now includes ruledescription. The alertcount field has been removed and replaced with totalalertsreceived and uniquealertsafter_deduplication in the response for obervability rule execution API.