Skip to main content

Entity-Data – Changed

The partial-properties endpoint is now unconditionally available to all callers. Request/response schema is unchanged.

Affected Endpoints

  • POST /entitydataquery/api/v2/entity/drafts/partial-properties

Entity-Data – Added

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 token instead of a bare array. Omitting page options defaults to a page size of 100; page size accepts 1-500.

Affected Endpoints

  • POST /entitydataquery/api/v2/drafts-in-scope/search-entity-drafts-light

Entity-Data – Changed

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.

Affected Endpoints

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

Screening – Added

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.

Additionally, the ConfigurationSetId field is now exposed in the Ongoing Screening results callback, enabling adapters to identify which configuration set a screening result belongs to.