Data API : Release Notes
Data API Release Notes act as the official “news feed” for your development team, documenting every new feature, improvement, and fix we apply to the system. This log provides full transparency on what has changed, helping your developers leverage new capabilities immediately while ensuring your existing integrations remain stable and interruption-free.
User Attestation events in Conversations and Interactions
Date : August 24, 2026
Category : New feature
Summary
Attestation and consent acknowledgments from the web assistant are now exposed through the API. When a user accepts an attestation form, you get one interaction recording the acknowledgment and one conversation row so that interaction keeps referential integrity with the /conversations entity.
Technical Details
- Interactions:
type = INTERACTION_TYPE_USER_ATTESTATION,actor = user,label = Null,parent_interaction_id = Null. The title of the form the user accepted is indetail.detail;detail.platform_namecarries the assistant’s friendly name. - Conversations:
type = CONVERSATION_TYPE_USER_ATTESTATION,route = Notification,detail = Null,primary_domain = Null. - This is a web-only event, so
platformis a web surface value such asmovewebchat.
platform_name added to the Interactions detail object
Date : July 28, 2026
Category : New field
Summary
Every record in the /interactions entity now carries detail.platform_name — the friendly name of the AI Assistant that served the interaction, as configured in Moveworks Setup. If your org runs more than one assistant, use this field to attribute interactions to the right one.
Technical Details
- Field:
detail.platform_name - Coverage: returned for all interaction types, including bot messages, button clicks, link clicks, file uploads, UI form submissions and user attestations.
- Null cases: interactions recorded before this field was released, and assistants with no friendly name configured.
- This is additive.
platform(the chat surface, for exampleslackormsteams) is unchanged and is still a top-level field.
Notifications data via API
Date : April 1, 2026
Category : New feature
Summary
- Every notification , ticket interception, and channel resolution will now be visible in the API.
- Data API will now have a 30 day TTT. (this means that you can only get data up to 30 days back by using MW Data API)
This new entity will allow you to have data for :
- System-generated notifications (e.g., password reset alerts)
- Employee communications tool messages.
- Creator Studio-initiated messages. (including ambient agents)
- Concierge or plugin-based notifications (e.g., ITSM status updates, comments)
- External integration notifications (e.g., ITSM approval workflows)
Technical Details
Please refer this post : https://community.moveworks.com/stakeholder%2Dtools%2Dexi%2Dmw%2Dsetup%2Dks%2Danalytics%2D115/notifications%2Dapi%2Dconversations%2Dentity%2D3294
Interactions API Update
Date: November 25, 2025 Category: New Feature
Summary
The Interactions API has been enhanced to include free-text user comments originating from CSAT (Customer Satisfaction) campaigns. This update provides programmatic access to qualitative user feedback, enabling deeper sentiment analysis and direct visibility into end-user experiences.
Technical Details
Developers can now retrieve specific user feedback text by filtering for UI Form Submission events.
- Data Field: The user’s specific comment is located in the
detail.contentfield.
Filtering Logic To ingest this specific data, configure your API calls to match the following criteria:
Example Interpretation
When iterating through the interaction logs, a matching event indicates a user has submitted a free-text response to a CSAT prompt. The value found within detail.content represents the raw text of that feedback.