Event Notifications – Changed
Requests to create a webhook containing an empty list of event types will now be considered invalid and return HTTP Status Code 400 (Bad Request).
Requests to create a webhook containing an empty list of event types will now be considered invalid and return HTTP Status Code 400 (Bad Request).
Marked endpoint as obsolete. There is no termination date set yet but it is recommended to use /api/documentmanagement/entity/paged or /api/documentmanagement/entity/paged/lite instead.
/documentmanagementquery/api/documentmanagement/entity/{entityId}New V3 api
Added new endpoint to retrieve grouped lookup options for fields
/portaltenantquery/api/portal-users/userdetails/{id}/nolinks - Gets Portal User details without linked entities (returns details of portal user without linked entities)Get upload url for transaction batch
Added the Username property to UserAuthorizationProfileDto used by the below query endpoints:
Added optional param to omit entity name from properties and add Entity Name to response in query endpoint to search entities by entity IDs:
The event notifications produced by the Command API endpoints have been updated. The Payload object within the event notification now includes the EventCreated and UserId properties.