Data API Release Notes

New FAQ metadata in the plugin resources detail object

Date: November 10, 2026
Category: New fields

What changed

Plugin resource records of type RESOURCE_TYPE_INTERNAL_KNOWLEDGE now carry a populated detail object for FAQs surfaced by Enterprise Search. Before this change, detail was always null for this resource type, so there was no way to tell which FAQ the AI Assistant showed. You can now see the title, domain and text of each FAQ, so you can track FAQ adoption and effectiveness across your business lines.

• name — Title of the FAQ.
• domain — Resource domain of the FAQ, for example IT, HR or FINANCE. It uses the same values as the domain key on knowledge, form, ticket and approval resources, so you can group FAQ usage alongside those resource types.
• snippet — FAQ text that the AI Assistant used in its response.

Example record:

{
  "id": "Xc4TmQ8vLp2N",
  "resource_id": "7f3a9c2e41b84d6f",
  "type": "RESOURCE_TYPE_INTERNAL_KNOWLEDGE",
  "plugin_call_id": "sKCETbg7VR9w",
  "interaction_id": "AbG1JsIP7cQd",
  "conversation_id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "cited": true,
  "detail": {
    "name": "What is Flybuys",
    "domain": "IT",
    "snippet": "Customer loyalty program where customers are provided with points after spending at eligible businesses."
  },
  "created_time": "2026-11-10T09:12:06.001Z",
  "last_updated_time": "2026-11-11T03:41:22.507Z"
}

Technical details

• Fields populated: detail.name (string), detail.domain (string), detail.snippet (string), for records where type is RESOURCE_TYPE_INTERNAL_KNOWLEDGE.
• Effective date: November 10, 2026. Only records created from this date onward carry the new detail values. There is no backfill; records created before this date keep detail: null.
• No url key: FAQ records do not include url, unlike knowledge article, file and ticket records. An FAQ’s source URL points to the document that holds many FAQs, not to the individual FAQ, so it can’t identify which FAQ was shown. Use name or resource_id to count or group individual FAQs.
• Enterprise Search FAQs only: FAQs surfaced by the Self Knowledge plugin (questions about the AI Assistant’s own capabilities) still return detail: null. These are a very small share of RESOURCE_TYPE_INTERNAL_KNOWLEDGE records.
• Keys can be absent: as with other resource types, a key is left out when its value isn’t available. For example, snippet is absent when the FAQ was shown by a plugin that doesn’t return FAQ text.
• Volume and joins: no records are added or removed, and the type, resource_id and cited values are unchanged. conversation_id, interaction_id and plugin_call_id join to the Conversations, Interactions and Plugin Calls endpoints exactly as they do for other resource types.
• This is an additive, non-breaking change. If your integration reads RESOURCE_TYPE_INTERNAL_KNOWLEDGE records, confirm that nothing in your ingestion or reporting expects detail to be null for them. See Breaking vs. non-breaking changes.

agent_id and agent_name added to Interactions detail object

Date: October 29, 2026
Category: New fields

Summary

Two new fields — agent_id and agent_name — are being added to the detail object returned by the /interactions endpoint. These fields allow you to attribute each interaction to the specific Productivity Assistant or the Universal Assistant that handled it.

• agent_id — Stable UUID for the Productivity Assistant that handled the interaction. For interactions handled by a configured Productivity Assistant, this field contains the assistant’s unique identifier. For Universal Assistant interactions, agent_id is null — there is no ID to reference when no Productivity Assistant is involved. Use agent_id as your referential key when building PA-specific insights on top of the Interactions endpoint; it never changes, even if an admin renames the assistant.
• agent_name — Human-readable display name of the assistant, as configured in Moveworks Setup. Returns "AI Assistant" for Universal Assistant interactions. Returns the assistant’s configured name (for example, "Talent Insights") for Productivity Assistant interactions.

Technical Details

• Fields added: detail.agent_id (string, UUID), detail.agent_name (string)
• Effective date: October 29, 2026. agent_id and agent_name will not appear in the detail object for interactions recorded before this date — these fields are only populated for incremental interactions from the release date onwards. There is no backfill for historical records.
• Null behavior for Universal Assistant interactions: agent_id is always null for Universal Assistant interactions — there is no ID to reference when no Productivity Assistant is involved. agent_name returns "AI Assistant" for these interactions, regardless of whether Productivity Assistants are configured for the org.
• This is an additive, non-breaking change. No existing fields are removed, renamed, or restructured.

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 in detail.detail; detail.platform_name carries 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 platform is a web surface value such as movewebchat.

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 example slack or msteams) is unchanged and is still a top-level field.

Notifications data via API

Date : April 1, 2026
Category : New feature

Summary

1. Every notification , ticket interception, and channel resolution will now be visible in the API.
2. 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

FAQs : https://help.moveworks.com/ai-assistant/analytics-performance/data-api/notifications-data-via-api-faq

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.content field.

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.