Intapp Products
All Intapp Release Notes (30)
- Feb 24, 2026
- Date parsed from source:Feb 24, 2026
- First seen by Releasebot:Mar 3, 2026
2602 - February Release
Publication APIs now use site specific endpoints, replacing environment or region based paths, and are listed on the Swagger page. Legacy endpoints will remain temporarily but migration is advised. New DealCloud REST API endpoints enable programmatic template report creation, status checks, and downloads for automated workflows.
Site-Specific Publication API Endpoints
⚠️
Integration updates required to Publication APIsThe Publication API endpoints are now site-specific, replacing the previous environment/region-based endpoint structure. The new endpoints are also available on the standard site Swagger page. Integrations & requests should be updated to the site-specific endpoints. Legacy environment-based endpoints will continue to function temporarily, but clients should migrate to the new site-specific domains as soon as possible.
Template Report APIs
Three new endpoints have been added to the DealCloud REST API which allow administrators to programmatically generate template reports, allowing for more robust workflow automation. These endpoints allow you to identify existing template reports, initiate the generation of a report using a template, check the status of generation, and download the completed report
Original source - Feb 1, 2026
- Date parsed from source:Feb 1, 2026
- First seen by Releasebot:Mar 3, 2026
2502 - February Release
Proxy User Metadata in Publications API
The Publications API now includes user proxy data in events, providing improved visibility around user actions in cases where changes were made by a proxy user. When a proxy is used, the response now includes lines for proxyUserId and proxyUserEmail. The principal user still appears in the modifiedById and modifiedByUserEmail metadata.
Original source All of your release notes in one feed
Join Releasebot and get updates from Intapp and hundreds of other software products.
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
Publications API
The Publications page on DealCloud now has an "Open Swagger" button that directly opens the Publications Swagger page for Publication API call testing.
Original source - January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
Data APIs - Time Zone Support
When retrieving data through an API, users can include the new dateTimeBehavior parameter to return date and time data in their local time zone rather than UTC. The parameter can be used when writing or updating data as well, automatically converting date and time fields as appropriate. The dateTimeBehavior parameter has two possible values:
- 0: Uses UTC. Does not need to be specified. Default behavior
- 1: Uses the API user's local time zone, or the client site time zone for date-only fields.
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
User Activity API Now Tracks Principal User
The User Activity API now includes a new principalUserName parameter, which shows the principal user in cases of user proxying. This change provides more complete context when tracking user proxying.
Original source - January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
2407 - July Release
Default Topics Appear on the Publications Page UI
The three default publication topics - default-data, default-users, and default-schema are now shown on the Publications page, offering administrators a clearer view into the events streaming from DealCloud.
Original source - January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
Field Filtering for Publication Events
When editing a Publications topics, administrators can now choose which fields they receive Publication events for. In the Field Settings (optional) column, clicking Edit allows administrators to select the fields for which the API should stream updates. After configuring field filters, the number of fields selected is shown in the Selected column.
See more
Original source - January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
Relationship Intelligence APIs
New API endpoints are available that enable you to deliver email and meeting metadata to DealCloud for processing and analysis by the Relationship Intelligence service (released in 2401).
Documentation now available here
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
Core
Changes
The User object model now includes a reference to the UserEntryID, which may not always be the same as the EntryID for the user entry.
The /allHistory endpoint now tracks reference change events such as those caused by merged entries. For example, if two records are merged and the resulting record has an updated value that is referenced by other records, the records that reference that merged entry will be shown as modified by the /allHistory endpoint.
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
API Change History Settings
API admins gain richer Change History visibility with new field type support in Change History Settings, improving audit log accuracy for API updates. If an integration floods updates or repeats values, those fields may be excluded from API history and show Modified By as Integration Check Service, with guidance to fix the flow before re enabling.
Release Notes
API administrators can now view additional field types on the Change History Settings page (Site Settings → Firm Settings → API Audit History Settings → Change History Settings), allowing them to keep track of audit log enablement and disablement for API updates more accurately.
For integrations sending a large volume of updates or repeat values to fields, admins may notice those fields are automatically excluded from API history tracking. For those fields, the Modified By column will show Integration Check Service. We encourage admins to resolve the integration flow before re-enabling them for API history tracking.
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
Relationship Intelligence APIs
- New API endpoints are available that enable you to deliver email and meeting metadata to DealCloud for processing and analysis by the Relationship Intelligence service. For organizations that do not have a supported Microsoft Exchange connection or prefer to communicate through APIs, use this capability to deliver the metadata that is needed for identifying the connections between your organization and external contacts and analyzing and scoring those relationships.
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
Publications API
Schema Versioning: A new schemaVersion property has been added to data and schema event responses. This property denotes the current site schema version.
Calculated Events: A new isCalculated boolean attribute has been added to the payload of data events. If the event reflects a calculation update, the value of this attribute is set to true.
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
User Management API
DealCloud unveils new User Management APIs for batch add/remove of users to groups, retrieve users by group, and API-based user invitations. Security boosts introduce 2FA and IP restrictions at the user level.
2. Add/Remove Users from Groups
Two new endpoints allow administrators to quickly add or remove one or more users from one or more user groups. These endpoints append user group assignments (and not replace), making it easier to iteratively manage entitlements and roles.
- To add users to user groups, use the following endpoint:
PUT /api/rest/v1/management/user/group- To remove users from groups, use the following endpoint:
DELETE /api/rest/v1/management/user/group3. Retrieve Users by User Group ID
A new optional query parameter called userGroupID has been added to the GET /user endpoint, which allows the API to retrieve a list of users using a user group ID. This enhancement provides a new way to retrieve lists of users so administrators can manage their roles, permissions, and user groups effectively.
4. User Invitation API
A new API endpoint has been added to User Management - POST /user/invite - allowing users to be invited to a site through an API. The invitation can be set to either Permanent ("type": 0) or Temporary ("type": 1). If a temporary invitation is sent, a duration must also be set in days (e.g. "duration": 10).
5. Security Config Enhancements
The User Management APIs can now be used to configure two-factor authentication and IP restrictions at the user level. This update allows administrators to automate the configuration of 2FA and IP restrictions via external systems and into DealCloud.
- TwoFactorEnabled - When set to True, 2FA is enabled for the user. This cannot be disabled via the API.
- IpRestrictionsEnabled - When set to True, the user's access is restricted to only whitelisted IP addresses. This cannot be disabled via the API.
- Dec 1, 2025
- Date parsed from source:Dec 1, 2025
- First seen by Releasebot:Mar 3, 2026
2512 - December Release
Case sensitive tracking for API updates now detects text casing changes and applies them, aligning API behavior with form edits. A new warning when disabling an API key prevents accidental downtime by informing users that active connections will break and a new key is required.
Case Sensitive Tracking for API Updates
The REST API now tracks case changes to text fields. Previously, updating a field from "Example Company" to "EXAMPLE COMPANY" would not register as a change, causing issues for field updates that rely on precise casing such as brand names, codes, identifiers, and proper nouns.
With this update, case changes sent by the API are tracked and reflected in the product, matching the experience of entry form updates.
Warning When Disabling API key
If a user attempts to toggle off the Enable API Key option in their User Profile while the API key is already enabled, a new warning message now appears to inform them that doing so will break all active API connections using those credentials. It also clarifies that the same API key cannot be re-enabled, so any active integrations would need to be manually updated with a new key. This confirmation step is intended to prevent accidental downtime by ensuring that disabling an API key is an intentional decision.
Original source