Intapp Release Notes
Last updated: Jan 21, 2026
Intapp Products
All Intapp Release Notes (25)
- January 2026
- No date parsed from source.
- First seen by Releasebot:Jan 21, 2026
Backend Security Upgrade - OAuth Token Update
DealCloud rolls out a major backend security upgrade across environments. Most users won’t notice changes, but some may see brief interruptions in OAuth token generation and authentication. Monitor integrations and review OAuth guidelines; contact Support if issues arise.
Backend security upgrade
As part of our ongoing commitment to enhancing system security and integrity, we're rolling out a major backend security upgrade across our environments. While most clients will not experience any changes, some may notice interruptions in their integrations, specifically related to the OAuth token generation and authentication process.
While we're aiming to keep interruptions minimal and ensure backward compatability, please monitor your integrations for any issues. Please review and ensure you're adhering to the guidelines in our
Original source Report a problem
OAuth Token documentation. If you encounter any issues, please reach out to the DealCloud Support Team for assistance. - 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 Report a problem All of your release notes in one place
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
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 Report a problem - 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 Report a problem - 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 Report a problem - 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.