Notifications data via API is going live on 1st April’2026.
Check out this post for more information : https://community.moveworks.com/stakeholder-tools-exi-mw-setup-ks-analytics-115/big-news-proactive-insights-are-coming-to-the-data-api-3286

V1 Data API is now released

The Data API is now available in the V1 version. If you are still using the Beta2 or Beta1 version please migrate your active workflows to this version.

For customer using Beta2

There is no change in the API structure, you can even use the same credentials that were shared with you during the beta program. The only change you need to make on your end is to update the API URL

Beta2 URL : https://api.moveworks.ai/export/v1beta2/records/conversations

V1 URL : https://api.moveworks.ai/export/v1/records/conversations

For customer using Beta1

Beta1 API is severely outdated at this point. If you are still using this API migrate to the beta2 version as fast as possible.

We have published a new course on Data API here. This aims to give you a complete overview of what is Data API and what can you achieve using Data API.

We have recently introduced a new capability to support $count in Data API. This query provides details on the number of records that are available based on the filter that is parsed to a Data API entity. Read more here : link

Overview

The Data API is a product offered by Moveworks that is designed to allow customers to ingest AI Assistant conversations and interaction data through a REST API. The Data API exposes all interactions, including user utterances, button clicks, link clicks, and UI form submissions. It also provides information on the plugins invoked by the LLM, resources used to generate summarized responses, and users who have been ingested into Moveworks and have access to the AI Assistant.

What is a rest API?

A REST API (Representational State Transfer Application Programming Interface) enables systems to communicate over HTTP using a set of architectural principles. It is stateless, meaning each request from a client to the server must contain all necessary information. The key HTTP methods used are GET (retrieve data), POST (create data), PUT (update data), and DELETE (remove data). Resources are accessed via standard URLs, and JSON format is typically used for data exchange. REST APIs are known for their simplicity, scalability, and flexibility, making them ideal for web services and mobile applications.

Learn more about REST API here.

API version

The current version of the Data API is v1, served under https://api.moveworks.ai/export/v1/records/. The earlier v1beta1 and v1beta2 versions are superseded — migrate any remaining workflows to v1. To read more on the API lifecycle management please refer to this documentation.

Which REST Endpoints are exposed via Data API

The Data API exposes base tables related to AI Assistant conversations data. The following tables are exposed through individual REST endpoints. Only the GET method is supported on these endpoints.

Name of the table	Data exposed through the tables	URL
Conversations	Conversations are the top level objects over all interactions. Conversations are grouped based on the context of the interaction. All interactions within a conversation share the same conversation ID.	https://api.moveworks.ai/export/v1/records/conversations
Interactions	All user and AI Assistant exchanges are defined as interactions. These are the building blocks for a conversation.	https://api.moveworks.ai/export/v1/records/interactions
Plugin calls	Whenever a plugin is called by the assistant in a conversation all of these entries are recorded in this table. The plugin calls object provides details on the plugin name, whether the plugin served the request or not, and whether the plugin was used in the interaction.	https://api.moveworks.ai/export/v1/records/plugin-calls
Plugin resources	Resources used by the plugin to serve the end user are recorded in this table. The resource object provides details on the Service portal name, URL, and ID of the resource. There can be multiple resource types, such as Knowledge, Forms, Users, or Tickets.	https://api.moveworks.ai/export/v1/records/plugin-resources
Users	Users who are ingested into Moveworks are stored in this table. This table provides details on the ingested user’s ID from the end systems that are configured in identity setup, which can be used to pull additional information from external systems such as Okta or Active Directory.	https://api.moveworks.ai/export/v1/records/users

How is the Data Model structured

The Data Model follows an hierarchical approach to allow additional data for nested object. The relationship can be understood by the following image.

The parent object shares 1-Many relationship with the subsequent child object. Users API fetches data from a standalone table which provides details around the user ingested into Moveworks.

API structure

All REST endpoints will respond in JSON format defined by OData. Each JSON object represents a new unique entry in that table

{
"odata.context": "...",
"odata.nextlink": "...",
"value" : [
	{ //object 1
	},
	{ //object 2
	}
	]
	
}

If there is no entries present in the table, the value array is empty.
All attributes in each entity either contains a “value” or will be NULL . There will be no empty strings or empty JSON if data is not present for a certain field.
Most attributes are exposed as STRING, nested JSON with STRING key <> value pair, or array of STRING. The only exceptions are the flag fields, which are exposed as JSON booleans: served and used on plugin calls, cited on plugin resources, and access_to_bot on users.
Timestamps are ISO 8601 strings in UTC, for example 2026-09-15T09:12:04.118Z.

For the full interactive API reference, including try-it functionality, refer here.

Data Dictionary

The following tables cover what attributes are available in through individual REST API’s. To understand the exact attribute names for each REST endpoints please refer to the API documentation.

Conversations

Field name	Description
ID	UUID assigned by the system to a conversation. Conversations are grouped based on the context of interactions. All interactions within a conversation share the same conversation ID.
User ID	User record ID assigned by the system to a user.
Conversation Domain	Primary domain detected by an LLM model after going through all detected domains of free text interactions belonging to a particular conversation.
Route	This field contains details on how a conversation was started either through DM, Notification engagement, Ticket interception engagement, or Channel resolver engagement.
Type	For system-triggered conversations (notifications, ticket interception, channel interception), this field captures the specific conversation type. CSAT survey conversations use `CONVERSATION_TYPE_CSAT_NOTIFICATION`. See the conversation type reference for the full list. Null for user-initiated DM conversations.
Detail	JSON object containing metadata specific to the conversation type. Contents vary by `type` (e.g., `ticket_id` for ticket notifications, `campaign_id`/`campaign_name` for comms notifications). Null for `CONVERSATION_TYPE_CSAT_NOTIFICATION` and DM conversations.
Created time	Timestamp when the conversation was initiated.
Last updated time	Timestamp when the conversations entry is last updated in this table.

Fields inside the conversation `detail` JSON object

detail is populated only for system-triggered conversations, and its keys depend on type. User-initiated DM conversations return Null.

Field name	Description
`ticket_id`	Ticket the conversation is about. Returned for the ticket notification types and for `CONVERSATION_TYPE_TICKET_INTERCEPTION`.
`campaign_id`	Campaign that sent the message. Returned for `CONVERSATION_TYPE_COMMS_NOTIFICATION`.
`campaign_name`	Name of that campaign. Only available for campaigns created after February 20, 2026.
`usecase_id`	Creator Studio usecase that triggered the notification. Returned for `CONVERSATION_TYPE_AMBIENT_AGENT_NOTIFICATION` and `CONVERSATION_TYPE_EVENTS_NOTIFICATION`.
`usecase_name`	Name of that usecase.
`type`	Resource sub-type of the approval. Returned for `CONVERSATION_TYPE_APPROVAL_REQUEST_NOTIFICATION`.
`source`	External system the approval came from. Returned for `CONVERSATION_TYPE_APPROVAL_REQUEST_NOTIFICATION`.
`domain`	Domain of the approval. Returned for `CONVERSATION_TYPE_APPROVAL_REQUEST_NOTIFICATION`.
`channel_id`	Channel the question was posted in. Returned for `CONVERSATION_TYPE_CHANNEL_INTERCEPTION`.
`channel_name`	Name of that channel.
`content`	Text that triggered the interception: the channel message for `CONVERSATION_TYPE_CHANNEL_INTERCEPTION`, the ticket description for `CONVERSATION_TYPE_TICKET_INTERCEPTION`.

For the full list of type values and which of them return an empty detail, see the conversation type reference.

Example conversation records

A comms notification:

{
  "id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "route": "Notification",
  "primary_domain": null,
  "type": "CONVERSATION_TYPE_COMMS_NOTIFICATION",
  "detail": {
    "campaign_id": "86ccdb47-dde0-45c8-abca-858c8df9889e",
    "campaign_name": "Q3 security training"
  },
  "created_time": "2026-09-15T07:25:17.202Z",
  "last_updated_time": "2026-09-16T03:43:02.908Z"
}

A user-initiated DM conversation, where type and detail are Null:

{
  "id": "MdA951Y2pQwe",
  "user_id": "11793429900163968620",
  "route": "DM",
  "primary_domain": "IT",
  "type": null,
  "detail": null,
  "created_time": "2026-09-15T09:12:04.118Z",
  "last_updated_time": "2026-09-16T03:43:02.908Z"
}

CSAT data

CSAT (Customer Satisfaction) data is exposed across the Conversations and Interactions entities. The table below summarizes where each piece of CSAT data lives.

What you want	Entity	How to find it
CSAT survey was sent to a user	Conversations	`route = "Notification"` and `type = "CONVERSATION_TYPE_CSAT_NOTIFICATION"`
User engaged with the survey	Interactions	Join on `conversation_id` of CSAT conversations and filter `actor = "user"`
User’s free-text comment	Interactions	`type = "INTERACTION_TYPE_UIFORM_SUBMISSION"`, `label = "mw_form"`, `detail.detail = "CSAT Feedback"`. Comment text is in `detail.content`.
User’s star rating	Interactions	Captured as a button click on the rating buttons in the CSAT survey message. The button name is in `detail.content`.

CSAT surveys are sent weekly to a sampled subset of active users with a 1–5 star rating scale. Users can update their rating; only the latest rating is reflected in the analytics app. See Customer Satisfaction Survey (CSAT) for survey behavior and eligibility.

Interactions

Field name	Description
ID	UUID assigned by a system to a interaction. An interaction is either an input from a user to the system, or a response from the system the the user.
Conversation ID	ID of the parent conversation.
User ID	User record ID assigned by the system to a user.
Actor	This field differentiates user v/s AI Assistant interactions.
Platform	This field denotes the platform where the interaction took place. For example: slack, msteam
Type	This field defines the type of the interaction. The interaction can belong to one of the following types. `INTERACTION_TYPE_FREE_TEXT` - user types an utterance `INTERACTION_TYPE_CONTENT_UPLOAD` - user uploads content, for example a file `INTERACTION_TYPE_BOT_MESSAGE` - text of the AI Assistant response to a user `INTERACTION_TYPE_UIFORM_SUBMISSION` - user submits a UI form. Every form variant shares this one type; use `label` to tell them apart. `INTERACTION_TYPE_LINK_CLICK` - user clicks on a URL link (Moveworks wrapped links or Unwrapped Service portal link), citation, global action emoji (For example: Helpful, Unhelpful, Information) or a link presented as a button. `INTERACTION_TYPE_BUTTON_CLICK` - user clicks on a button in chat `INTERACTION_TYPE_USER_ATTESTATION` - user accepts an attestation or consent form in the web assistant. Web-only. `label` is always Null and the title of the form the user acknowledged is in `detail.detail`.
Label	This field defines the label for UI form submission interaction type. This can contain any one of the following values feedback - User has submitted a “feedback” form by clicking on the Helpful/Unhelpful button file_ticket - In-chat fillable “file ticket” form submitted by the end user. mw_form - User has submitted a Internal MW form. For example: Change language form. handoff - User has submitted a form after clicking on the “Get help” button. `label` is Null for every other interaction type, including `INTERACTION_TYPE_USER_ATTESTATION`.
Parent Interaction ID	Parent interaction ID for AI Assistant messages and User follow-up actions as button clicks, link clicks & UI form submission.
Detail	This is a JSON object which contains metadata per interaction type. The detailed description of each field is covered in the below table.
Created time	Timestamp when the interaction was initiated.
Last updated time	Timestamp when the interaction entry is last updated in this table.

Fields inside the “detail” JSON object

Field name	Description
content	This field contains the free form text, link URL, Button name according to interaction type. For feedback it contains the free text feedback provided by the end user. In case of label = “mw_form” and detail = “CSAT feedback” - This field will contain the free text message provided by the end-user in the form.
domain	This the interaction level detected domain . Domain is only predicted for free form text interaction type. In some cases, domain of individual utterances may differ from the primary domain detected per conversation.
entity	This field contains the topic as detected per each interaction. Topic is only predicted for free form text interaction type.
type	This field indicates which type of resource were accessed during an link click interaction.
detail	This field indicates the form name which was submitted. For feedback this attribute contains either Helpful (or) Unhelpful indicating which feedback form was filed.
resource_id	This field provides the resource ID that was accessed by the end user during an link click interaction, or when a user submits a ticket via UI form INTERACTION_TYPE_LINK_CLICK INTERACTION_TYPE_UIFORM_SUBMISSION
file_types	This field provides list of types of files that were uploaded during a file upload interaction (INTERACTION_TYPE_CONTENT_UPLOAD). We do not record the file names as user can also upload a private file
platform_name	Friendly name of the AI Assistant that served the interaction, as configured in Moveworks Setup. Present on every interaction type. Use it to attribute interactions when your org runs more than one assistant. It is Null for interactions recorded before this field was released, and for assistants with no friendly name configured.

Which `detail` keys appear for each interaction type

The detail object is shaped by the interaction. Only the keys listed below are returned for a given type/label combination; keys that do not apply are absent rather than Null.

`type`	`label`	Keys in `detail`
`INTERACTION_TYPE_FREE_TEXT`	Null	`content`, `domain`, `entity`, `platform_name`
`INTERACTION_TYPE_BOT_MESSAGE`	Null	`content`, `platform_name`
`INTERACTION_TYPE_BUTTON_CLICK`	Null	`content`, `platform_name`
`INTERACTION_TYPE_LINK_CLICK`	Null	`resource_id`, `type`, `platform_name`. Links that carry the raw URL (for example an unwrapped service portal link) also return `content`.
`INTERACTION_TYPE_CONTENT_UPLOAD`	Null	`content`, `file_types`, `platform_name`
`INTERACTION_TYPE_UIFORM_SUBMISSION`	`feedback`	`content`, `detail`, `platform_name`
`INTERACTION_TYPE_UIFORM_SUBMISSION`	`file_ticket`	`resource_id`, `type`, `detail`, `platform_name`
`INTERACTION_TYPE_UIFORM_SUBMISSION`	`handoff`	`detail`, `platform_name`
`INTERACTION_TYPE_UIFORM_SUBMISSION`	`mw_form`	`content`, `detail`, `platform_name`
`INTERACTION_TYPE_USER_ATTESTATION`	Null	`detail`, `platform_name`

For link clicks, detail.type carries the type of the resource behind the link. Alongside the plugin resource types, it can also be RESOURCE_TYPE_INTERNAL_LINK for assistant-internal actions such as GET_HELP, INFO and OTHER_HELP — these have no matching row in the plugin resources entity.

Example interaction records

A free-text utterance, showing the detected domain and topic plus the assistant that served it:

{
  "id": "PkO2Wd5nRv0-",
  "conversation_id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "actor": "user",
  "platform": "slack",
  "type": "INTERACTION_TYPE_FREE_TEXT",
  "label": null,
  "parent_interaction_id": null,
  "detail": {
    "content": "I need access to Zoom",
    "domain": "IT",
    "entity": "other_software_operations",
    "platform_name": "Ava"
  },
  "created_time": "2026-09-15T09:12:04.118Z",
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

An assistant response in the same conversation:

{
  "id": "AbG1JsIP7cQd",
  "conversation_id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "actor": "bot",
  "platform": "slack",
  "type": "INTERACTION_TYPE_BOT_MESSAGE",
  "label": null,
  "parent_interaction_id": "PkO2Wd5nRv0-",
  "detail": {
    "content": "I can request Zoom access for you. Shall I go ahead?",
    "platform_name": "Ava"
  },
  "created_time": "2026-09-15T09:12:06.442Z",
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

A file upload, showing file_types:

{
  "id": "1jG2YF0RfoM-",
  "conversation_id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "actor": "user",
  "platform": "movewebchat",
  "type": "INTERACTION_TYPE_CONTENT_UPLOAD",
  "label": null,
  "parent_interaction_id": null,
  "detail": {
    "content": null,
    "file_types": ["docx", "image/png"],
    "platform_name": "Ava"
  },
  "created_time": "2026-09-15T09:20:11.003Z",
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

A ticket filed through an in-chat form (label = file_ticket), where detail.detail holds the created ticket ID:

{
  "id": "sKCETbg7VR9w",
  "conversation_id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "actor": "user",
  "platform": "slack",
  "type": "INTERACTION_TYPE_UIFORM_SUBMISSION",
  "label": "file_ticket",
  "parent_interaction_id": "AbG1JsIP7cQd",
  "detail": {
    "resource_id": "123456789",
    "type": "RESOURCE_TYPE_FORM",
    "detail": "RITM-1234",
    "platform_name": "Ava"
  },
  "created_time": "2026-09-15T09:13:48.221Z",
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

A user attestation acknowledgment, where detail.detail holds the title of the form the user accepted:

{
  "id": "Zt4mQ9xLbEr1",
  "conversation_id": "attestation_issue_01",
  "user_id": "11793429900163968620",
  "actor": "user",
  "platform": "movewebchat",
  "type": "INTERACTION_TYPE_USER_ATTESTATION",
  "label": null,
  "parent_interaction_id": null,
  "detail": {
    "detail": "Acceptable Use Policy",
    "platform_name": "Ava"
  },
  "created_time": "2026-09-15T08:59:30.000Z",
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

Plugin calls

Field name	Description
ID	UUID assigned by the system to a plugin being called by AI Assistant for a interaction.
Interaction ID	ID of the interaction for which the plugin is called
Conversation ID	ID of the parent conversation.
User ID	User record ID assigned by the system to a user.
Plugin name	Name of the plugin being called. Native plugins For example: Knowledge Base, Create ticket, Grant Software Access Custom plugins : Represents the plugin name configured in Agent Studio For examples: Ariba_PTO_LOOKUP, Apply_Holiday_leave
Served	This field defines if the plugin was served to the end user. Plugin are considered served when they are offered to the end user through the AI Assistant response. For example: Knowledge base plugin is served when citations fetched by the plugin are used to generated the summarized response. Action plugins such as Create ticket are considered as “Served” when the workflow is initiated and is offered to the end users._
Used	This field defines if the plugin was used by the AI Assistant in the interaction. Plugins such as Knowledge base, Forms or productivity plugins if served are also considered as Used. Plugins such as File ticket, Update Approval are only considered as used if the end user has completed the workflow.
Created time	Timestamp when the plugin call was initiated.
Plugin update time	Timestamp of the last update for the plugin call.
Last updated time	Timestamp when the plugin call entry is last updated in this table

Example plugin call record

{
  "id": "sKCETbg7VR9w",
  "interaction_id": "PkO2Wd5nRv0-",
  "conversation_id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "plugin_name": "Grant Software Access",
  "served": true,
  "used": true,
  "created_time": "2026-09-15T09:12:05.330Z",
  "plugin_update_time": "2026-09-15T09:13:49.117Z",
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

Plugin resources

Field name	Description
ID	UUID assigned by the system to a resource being used by a plugin called during an interaction.
Plugin call ID	ID of the plugin being called.
Interaction ID	ID of the interaction.
Conversation ID	ID of the parent conversation.
User ID	User record ID assigned by the system to a user.
Resource ID	ID of the resource stored in Moveworks.
Type	This field represents the type of resource utilized by a plugin call. The type can be one of the following values. 1.RESOURCE_TYPE_FORM - Ingested forms from service desk. 2.RESOURCE_TYPE_TICKET - Tickets created by the AI assistant in service desk (or) fetched from the service desk. 3.RESOURCE_TYPE_FILE - Files ingested in Moveworks 4.RESOURCE_TYPE_KNOWLEDGE - Internal knowledge articles, FAQ, External knowledge ingested/configured in Moveworks. 5.RESOURCE_TYPE_APPROVAL - Approvals fetched from the Approval systems. 6.RESOURCE_TYPE_RECORD - Entries fetched from external systems through Queries in Agent Studio 7.RESOURCE_TYPE_IDENTITY_SYSTEM - Identity systems configured in Moveworks. 8.RESOURCE_TYPE_PERSON - User ingested into Moveworks. 9.RESOURCE_TYPE_SOFTWARE - Softwares provision workflows and entities configured in Moveworks. 10.RESOURCE_TYPE_GROUP - Distribution lists ingested into Moveworks 11.RESOURCE_TYPE_INTERNAL_KNOWLEDGE - Moveworks AI assistant internal knowledge. 12.RESOURCE_TYPE_UPLOADED_CONTENT - Content uploaded by end users. 13.RESOURCE_TYPE_ROOM - Room information ingested into moveworks 14.RESOURCE_TYPE_UNSPECIFIED - Unknown resource types. Please check the AI Assistant’s response to learn more.
Detail	This is a JSON object which contains metadata per resource type. The detailed description of each field is covered in the below table.
Cited	This field denotes if the utilized resource was cited in the AI Assistant response or not.
Created time	Timestamp when the resource was utilized by a plugin
Last updated time	Timestamp when the plugin resource entry was last updated in this table.

Field included in the “detail” JSON object

Field name	Description
Domain	This field denotes the resource domain configured in Moveworks Setup while configuring Content ingestion & Ticketing. Domain is defined for resources of types: RESOURCE_TYPE_APPROVAL RESOURCE_TYPE_FORM RESOURCE_TYPE_TICKET RESOURCE_TYPE_KNOWLEDGE
External Resource ID	Service portal ID for the resource of type RESOURCE_TYPE_KNOWLEDGE. This field can be used to join data from external system. Please note external resource ID is not provided for FILE & EXTERNAL KNOWLEDGE (Public knowledge enabled in Moveworks)
Name	Name of the resource being used by the plugin, populated for resources of types: RESOURCE_TYPE_FILE RESOURCE_TYPE_FORM RESOURCE_TYPE_KNOWLEDGE
Snippet	Exact snippet from the resource being used to provide the summarized response, populated for resource types RESOURCE_TYPE_FILE RESOURCE_TYPE_KNOWLEDGE
Source	Name of the external sources from which the resource is being fetched from, populated for resource types RESOURCE_TYPE_TICKET RESOURCE_TYPE_APPROVAL
Type	Contains sub-type of approval or type of the ticket creation : User initiated v/s AI Assistant initiated, populated for resource types RESOURCE_TYPE_TICKET RESOURCE_TYPE_APPROVAL
URL	External system URL of the resource, populated for resource types RESOURCE_TYPE_TICKET RESOURCE_TYPE_KNOWLEDGE RESOURCE_TYPE_FILE
Ticket type	ITSM ticket type of the resource, as classified in your service desk. For example: IT, HR, REQUEST. Populated for resource type RESOURCE_TYPE_TICKET

Which `detail` keys appear for each resource type

`type`	Keys in `detail`
`RESOURCE_TYPE_KNOWLEDGE`	`external_resource_id`, `name`, `url`, `snippet`, `domain`
`RESOURCE_TYPE_FILE`	`name`, `url`, `snippet`
`RESOURCE_TYPE_FORM`	`external_resource_id`, `name`, `domain`
`RESOURCE_TYPE_TICKET`	`ticket_type`, `type`, `source`, `url`, `domain`
`RESOURCE_TYPE_APPROVAL`	`type`, `source`, `domain`

The remaining resource types listed above do not carry a detail object; detail is Null for them.

Example plugin resource records

A cited knowledge article:

{
  "id": "85FnUWaV5pZQ",
  "resource_id": "12422565931618640979",
  "type": "RESOURCE_TYPE_KNOWLEDGE",
  "plugin_call_id": "sKCETbg7VR9w",
  "interaction_id": "AbG1JsIP7cQd",
  "conversation_id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "cited": true,
  "detail": {
    "external_resource_id": "KB10123423",
    "name": "Requesting Zoom access",
    "url": "https://starcompany.service-now.com/kb_view.do?sysparm_article=KB10123423",
    "snippet": "To request a Zoom licence, open the Software Access catalog item and choose the licence tier your team uses.",
    "domain": "IT"
  },
  "created_time": "2026-09-15T09:12:06.001Z",
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

A ticket created by the assistant, showing ticket_type:

{
  "id": "Rb7pLqA2ZcX9",
  "resource_id": "RITM-1234",
  "type": "RESOURCE_TYPE_TICKET",
  "plugin_call_id": "sKCETbg7VR9w",
  "interaction_id": "sKCETbg7VR9w",
  "conversation_id": "OqVm7dSD4uxD",
  "user_id": "11793429900163968620",
  "cited": false,
  "detail": {
    "ticket_type": "REQUEST",
    "type": "USER_INITIATED_TICKET",
    "source": "snow",
    "url": "https://starcompany.service-now.com/sc_req_item.do?sys_id=RITM-1234",
    "domain": "IT"
  },
  "created_time": "2026-09-15T09:13:49.117Z",
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

Users

The User API provides a daily export of your user roster. User records may repeat across days, with the last_updated_at field indicating the date of ingestion. We recommend using an upsert operation to ingest user data and handle repeated records efficiently.

Field name	Description
ID	User record id generated and stored in Moveworks for the end user
Email Addr	Email of the end user stored in Moveworks. This field is ingested from your systems and reflect the value present in your systems. Learn more about user profile here .
Access to AI Assistant	Denotes if the end user has access to Moveworks Assistant or not. This is evaluated through the AI Assistant access rule configured in Moveworks Setup.
First name	First name of the end user. This field is ingested from your systems and reflect the value present in your systems. Learn more about user profile here .
Last name	Last name of the end user.This field is ingested from your systems and reflect the value present in your systems. Learn more about user profile here .
User preferred language	User preferred language set from the end user. EN-US is the default value for this field
First interaction time	Time stamp for the first interaction for the end user.
Last interaction time	Time stamp for the latest interaction of the end user.
External Ids	This array contains External system details configured during identity ingestion Connector name : Name of the connector created in Moveworks Setup External ID : External ID from the source system Source : Identifier for the source system.
Last updated time	Last updated time for the user entry in this table.

Example user record

{
  "id": "11793429900163968620",
  "email_addr": "jordan.lee@starcompany.com",
  "first_name": "Jordan",
  "last_name": "Lee",
  "access_to_bot": true,
  "user_preferred_language": "EN-US",
  "first_interaction_time": "2025-11-02T14:07:51.000Z",
  "latest_interaction_time": "2026-09-15T09:20:11.003Z",
  "external_ids": [
    {
      "connector_name": "gsuite",
      "external_id": "jordan.lee@starcompany.com",
      "source": "GSUITE"
    },
    {
      "connector_name": "servicenow",
      "external_id": "62826bf03710200044e0bfc8bcbe5df1",
      "source": "SNOW"
    }
  ],
  "last_updated_time": "2026-09-16T03:41:22.507Z"
}

FAQ

Is there any applicable TTL ?

Yes, Data API has a TTL for 30 days. This means that you can use Data API to fetch data upto 30 days back.

What is the SLA for Data API to provide new data in the API response ?

The Data API follows a 24-hour SLA, consistent with the Moveworks Analytics platform. The table below outlines the expected SLA for our analytics pipelines. Please note that this SLA is subject to change based on the timing of the latest analytics pipeline run.

Region	Time ranges for interactions	SLA
UTC	2024-05-10 all day	2024-05-11 11pm
San Francisco (Pacific Daylight Time)	2024-05-09 5pm to 2024-05-10 5pm	2024-05-11 4pm
Chicago (Central Daylight Time)	2024-05-09 7pm to 2024-05-10 7pm	2024-05-11 6pm
New York (Eastern Daylight Time)	2024-05-09 8pm to 2024-05-10 8pm	2024-05-11 7pm
London (British Summer Time)	2024-05-10 1am to 2024-05-11 1am	2024-05-12 0am
Paris (Central European Summer Time)	2024-05-10 2am to 2024-05-11 2am	2024-05-12 1am
India (Indian Standard time)	2024-05-10 5:30am to 2024-05-11 5:30am	2024-05-12 4:30am
Melbourne (Australian Eastern Standard Time)	2024-05-10 10am to 2024-05-11 10am	2024-05-12 9am

Is there a sample data for Data API?

To access the sample data click on this link and download the “Sample responses” ZIP through the Github repository. This will contain JSON responses for - Conversations, Interactions, Plugin-calls, Plugin-resources and Users file. Please note we have anonymized the user details so the email address, first name and last name are replaced with a placeholder value.