# Qualtrics CoreXM MCP connector

The Qualtrics CoreXM connector brings tickets, users, activity logs and audit events into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works with them under their own Qualtrics CoreXM access.

Source: https://elaichi.ai/connectors/qualtricscorexm/

## Facts

| | |
| --- | --- |
| Application | Qualtrics CoreXM |
| Category | Survey |
| AI tools | 263 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Qualtrics CoreXM is connected

- Show me open Qualtrics CoreXM tickets assigned to my team
- Which tickets have sat in New for more than a week?
- Summarize yesterday's audit events for the research admins

## Connect Qualtrics CoreXM in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Qualtrics CoreXM.
2. Optionally set Share with, then press Connect.
3. Supply your own Qualtrics CoreXM app, then approve. Qualtrics CoreXM needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Qualtrics CoreXM tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Qualtrics CoreXM MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Qualtrics CoreXM MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Qualtrics CoreXM MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Qualtrics CoreXM MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Qualtrics CoreXM MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Qualtrics CoreXM to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Qualtrics CoreXM tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Qualtrics CoreXM through Elaichi

### Catch a follow-up ticket up after a call

Customer Experience. Ask for the Qualtrics CoreXM ticket raised from a customer's feedback, then update its status and notes once you have spoken to them, without opening the ticket screen.

### Find the tickets nobody has touched

Support. Search Qualtrics CoreXM tickets by status, team or group and ask which ones have sat in the same status for more than a week, then move them on.

### Keep the Qualtrics CoreXM user list tidy

IT. List every user, check who still has access, update a job change or create a new account for a starter, all from the chat window.

### Pull audit events before a review

Compliance. Ask for the audit events from a given week, start an audit export and download the files when they are ready, with no admin console visit.

### Load contacts and entities in bulk

Operations. Create a bulk entity import or a contact export, then check the activity log to confirm what actually ran and when.

### Explain what changed in the account

Research. Ask what activity log entries appeared yesterday, who made them and which type they were, and get a plain summary instead of a raw table.

## Elaichi vs Zapier MCP vs Composio for Qualtrics CoreXM

All three can connect Qualtrics CoreXM to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Qualtrics CoreXM tools | Allow or restrict single Qualtrics CoreXM tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Qualtrics CoreXM call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Qualtrics CoreXM to Claude?

First connect Qualtrics CoreXM in Elaichi, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. Qualtrics CoreXM needs an OAuth application registered inside your own Qualtrics CoreXM account, so one admin brings a client ID and secret once when setting up the connection. After that, every person simply signs in with their own Qualtrics CoreXM login and nobody else handles a key.

### Does Qualtrics CoreXM work with ChatGPT and Cursor as well as Claude?

Yes. Once Qualtrics CoreXM is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Qualtrics CoreXM once and every client picks it up.

### What can an AI agent actually do with my Qualtrics CoreXM data?

It can list and search Qualtrics CoreXM tickets, open one by its ID, update it or move it to another status, and show you the teams and groups tickets belong to. It can list, create, update or remove Qualtrics CoreXM users, read activity logs and audit events, start audit and contact exports and run bulk entity imports. Short, concrete asks such as open tickets for my team this week work better than long sentences.

### Does connecting Qualtrics CoreXM give the AI access to every ticket and user?

No. Every call into Qualtrics CoreXM runs as the person who signed in, so the agent sees only the tickets, users and audit events that person can already see in Qualtrics CoreXM. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.

### Can my team share one Qualtrics CoreXM connection?

Yes. One admin connects Qualtrics CoreXM in Elaichi, brings the client ID and secret once, and shares the connection with a team, so nobody else ever handles a credential. Each teammate still signs in to Qualtrics CoreXM as themselves, so the audit log names the real person behind every ticket update.

### Can I stop an agent from deleting or changing things in Qualtrics CoreXM?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting a Qualtrics CoreXM ticket or removing a user while leaving reading and searching open, and you set them on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Qualtrics CoreXM connection when someone leaves?

Offboarding that person in Elaichi ends their access to Qualtrics CoreXM through every client at once. A shared Qualtrics CoreXM connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Qualtrics CoreXM once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.

### Does the Qualtrics CoreXM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Qualtrics CoreXM is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Qualtrics CoreXM?

Yes. Both let Claude, ChatGPT or Cursor use Qualtrics CoreXM. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Qualtrics CoreXM call.

### How is Elaichi different from Composio for Qualtrics CoreXM?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Qualtrics CoreXM: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 263 Qualtrics CoreXM tools

Every tool below is callable through https://api.elaichi.ai/mcp once Qualtrics CoreXM is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Qualtrics CoreXM tickets** (List). Retrieve Tickets for Account. Using the provided query parameters, the API client can filter and retrieve a subset of tickets, instead of the entire collection if desired. This API call is only available to organizations that have purchased Closed Loop Follow Up. This API call will paginate up to a maximum of 10,000 tickets. To return more than this, use the Search Tickets endpoint with filters that split the tickets into sections of less than 10,000 each. OAuth scope: read:tickets.
- **Get single Qualtrics CoreXM ticket by ID** (Get). Retrieve Ticket. Use the ticket key to return the full ticket. This API call is only available to organizations that have purchased Closed Loop Follow Up. Organizations not enrolled will receive a 403 with the error code TIK_1.1. Ticket Priority Mapping This API will return the Ticket Priority as an integer, 0: Low, 1: Medium, 2:High. Required: id. id is the ticketKey. OAuth scope: read:tickets.
- **Delete a Qualtrics CoreXM ticket by ID** (Delete). Delete a Ticket. Using the ticket key, delete the ticket. This API call is only available to organizations that have purchased Closed Loop Follow Up. Organizations not enrolled will receive a 403 with the error code TIK_1.1. This API call can only be used by admins. Required: id. id is the ticketKey. OAuth scope: write:tickets.
- **Update a Qualtrics CoreXM ticket by ID** (Update). Update Ticket. Using the ticket key, update the ticket. There are a few key things to note. 1. At least one key is required in the body to update the ticket 2. Once assigned, you cannot unset the ownerId, ticketTeamId, or ticketGroupId 3. If a parameter is not included in the body, the field will not be updated. This API call is only available to organizations that have purchased Closed Loop Follow Up. Organizations not enrolled will receive a 403 with the error code TIK_1.1. Body fields: name, status, priority, ownerId, comment, ticketTeamId, ticketGroupId. Required: id. id is the ticketKey. OAuth scope: write:tickets.
- **Qualtrics CoreXM tickets search** (Search). Search Tickets. Using filters, search through tickets in your organization. This API call is only available to organizations that have purchased Closed Loop Follow Up. Organizations not enrolled will receive a 403 with the error code TIK_1.1. This API call will paginate up to a maximum of 10,000 tickets. To return more than this, use the Search Tickets endpoint with filters that split the tickets into sections of less than 10,000 each. Body fields: query, sort. Required: query. OAuth scope: read:tickets.
- **List all Qualtrics CoreXM ticket statuses** (List). Get Statuses. Retrieve statuses for your brand. This API call is only available to organizations that have purchased Closed Loop Follow Up. Organizations not enrolled will receive a 403 with the error code TIK_1.1. OAuth scope: read:tickets.
- **Qualtrics CoreXM ticket statuses replace** (Action). Set statuses for your brand. This API call is only available to organizations that have purchased Closed Loop Follow Up. Organizations not enrolled will receive a 403 with the error code TIK_1.1. Body fields: statuses. Required: statuses. OAuth scope: write:tickets.
- **List all Qualtrics CoreXM ticket teams** (List). Get List of Ticket Teams. Retrieve ticket teams for your brand. Administrator Request To use this call you must be a Qualtrics brand administrator or Qualtrics Ticket Admin OAuth scope: read:tickets.
- **List all Qualtrics CoreXM ticket groups** (List). Get List of Groups. Retrieve ticket groups for your brand. This API call is only available to organizations that have purchased Closed Loop Follow Up. Organizations not enrolled will receive a 403 with the error code TIK_1.1. Administrator Request To use this call you must be a Qualtrics Brand Administrator or Qualtrics Tickets Admin OAuth scope: read:tickets.
- **List all Qualtrics CoreXM users** (List). List Users. Return a list of all users in the collection. For more information about using the user APIs, see Managing Users. OAuth scope: read:users.
- **Get single Qualtrics CoreXM user by ID** (Get). Get User. Retrieve general information about a user. For more information about using the user APIs, see Managing Users. Administrator Request To use this call you must be a Qualtrics brand administrator. Required: id. id is the userId. OAuth scope: read:users.
- **Delete a Qualtrics CoreXM user by ID** (Delete). Delete User. Deletes a user. For more information about using the user APIs, see Managing Users. Administrator Request To use this call you must be a Qualtrics brand administrator. Required: id. id is the userId. OAuth scope: write:users.
- **Update a Qualtrics CoreXM user by ID** (Update). Update User. Updates user information. For more information about using the user APIs, see Managing Users. Administrator Request To use this call you must be a Qualtrics brand administrator. Body fields: username, email, firstName, lastName, userType, divisionId, status, language, timeZone, permissions, accountExpirationDate, identityProvider. Required: id. id is the userId. OAuth scope: write:users.
- **Create a Qualtrics CoreXM user** (Create). Create User. Creates a new user account. For more information about using the user APIs, see Managing Users. Administrator Request To use this call you must be a Qualtrics brand administrator. Body fields: username, password, firstName, lastName, userType, email, language, timeZone, divisionId, accountExpirationDate. Required: username, password, firstName, lastName, userType, email, language. OAuth scope: write:users.
- **List all Qualtrics CoreXM me** (List). Who Am I. Determine the user ID and other user information associated with an Qualtrics API token or a Qualtrics OAuth access token. Call must be against correct DataCenter Id To check the identity of the caller for an OAuth Token, the call must be made against the datacenter where the token was generated. This will be the same data center as the brand which created the client_id and client_secret for the OAuthClient. OAuth scope: read:users.
- **List all Qualtrics CoreXM activity log types** (List). List Event Types. Return a list of queryable audit event types in the account of the API client. Administrator Request To use this call you must be a Qualtrics brand administrator. Activity Types The activityTypes object shows the accepted activity type query params that can be used in the Get Activity Log endpoint (see: List Events). The additionalFilters property shows what query parameters can be used for the specific activity type. OAuth scope: read:activity_logs.
- **List all Qualtrics CoreXM activity logs** (List). List Events. Retrieve the collection of events by activity type and time interval. Activity Types Due to the different types of activities represented here, not every activityType query param will function on every query. To determine the activityType query parameters that can be used, see the Get Activity Log endpoint (see: List Activity Types). Required: activityType. OAuth scope: read:activity_logs.
- **List all Qualtrics CoreXM audit events** (List). List all audit event types. Returns a list of all audit event types. Administrator Request To use this call you must be a Qualtrics brand administrator OAuth scope: read:activity_logs.
- **Qualtrics CoreXM audit export files download** (Export). Retrieves a download for an export job. This will download the audit events export. Administrator Request To use this call you must be a Qualtrics brand administrator Returns the file content. Required: export_id, file_id. OAuth scope: read:activity_logs.
- **Create a Qualtrics CoreXM audit export** (Create). This will create a new export job to download audit event data. Administrator Request To use this call you must be a Qualtrics brand administrator Body fields: eventName, userId, startDate, endDate. Required: eventName, startDate. OAuth scope: read:activity_logs.
- **List all Qualtrics CoreXM audit exports** (List). Retrieves the status of an export job. Returns the status of an export job. Once the status is completed it will also return a file id to download the audit events. Administrator Request To use this call you must be a Qualtrics brand administrator Required: export_id. OAuth scope: read:activity_logs.
- **Create a Qualtrics CoreXM automation file** (Create). Upload a file for the automation to consume. Preview Functionality This API is not yet generally available. It is available as part of Early Access to receive feedback. Be aware that there may be significant changes to this API with short notice until the time that the API is made Generally Available. Sends multipart/form-data; MCP clients cannot send binary files. Required: automation_id. OAuth scope: write:automations.
- **Create a Qualtrics CoreXM bulk entity import** (Create). Create Bulk Entity Import. Create a Bulk Entity Import. JSON Body Size Limit The size of the JSON body accepted by this API call is 5 MB with a maximum of 1,000 refIds per import. The API returns an error if the size of the body or contact count exceeds these limits. For example, you can import 1,000 contacts. Or you can import 500 contacts with 500 transactions. Or 333 contacts with 333 transactions and 333 list memberships. Body fields: contacts. Required: directory_id, contacts. OAuth scope: write:contact_transactions.
- **Create a Qualtrics CoreXM contact export** (Create). Create Contact Export. Exports all the contacts within a directory or contact list that match the criteria provided in the filter. Filtering with multiple criteria The filter object allows you to refine your request by listing criteria that contacts must meet. When you need to apply multiple criteria, the filter object must include two specific components: - conjunction: A property that specifies how to combine your filter criteria. Body fields: format, embeddedData, contactListId, filter. Required: directory_id, format, embeddedData. OAuth scope: read:directory_contacts.
- **Qualtrics CoreXM contact exports download** (Download). Get Contact Export File. After the contact export has finished being processed, this API can be used to download the file. Required: directory_id, file_id. OAuth scope: read:directory_contacts.
- **Qualtrics CoreXM contact exports status** (Action). Get Contact Export Progress Status. Reports the current status of the contact export. Required: directory_id, progress_id. OAuth scope: read:directory_contacts.
- **List all Qualtrics CoreXM contact frequency rules** (List). List Contact-Frequency Rules. List all contact-frequency rules. Required: directory_id. OAuth scope: read:contact_frequency_rules.
- **List all Qualtrics CoreXM contact history** (List). Get Directory Contact History. Retrieve the history for contacts in a directory. For the last page of results, the value associated with nextPage will be null. This API call is only available to XM Directory users. Required: directory_id, contact_id, type. OAuth scope: read:directory_contacts.
- **List all Qualtrics CoreXM contact import reports** (List). Get Import Report for a Completed Import. Get a a generated report detailing the line by line success and failure of an import contacts request. Supported Only on XMD This API is only supported for users on XM Directory, not Genesis Contacts. Required: directory_id, import_id. OAuth scope: write:contact_transactions.
- **Qualtrics CoreXM contact transaction enrichments upsert** (Upsert). Upsert Contact Transaction with Enrichments. Upserts a transaction enrichment for a given transaction The combination of the context values, the provider, and the field make up the unique id for the enrichment. If these fields match then this api will update the existing enrichment otherwise a new enrichment will be created. Body fields: metric, source. Required: directory_id, transaction_id, metric, source. OAuth scope: write:contact_transactions.
- **Qualtrics CoreXM contact transactions append** (Action). Append Contact Transaction. Append information to a transaction. Appends Only, does not modify. This endpoint will not flush existing data, but rather append or override just the specified fields. Make sure the fields are inside the data field Body fields: data. Required: directory_id, transaction_id, data. OAuth scope: write:contact_transactions.
- **Create a Qualtrics CoreXM contact transaction** (Create). Create Contact Transaction. Create transactions for multiple contacts across multiple mailing lists with customized data. You can find the schema definition in the CreateContactTransaction Required: directory_id. OAuth scope: write:contact_transactions.
- **Delete a Qualtrics CoreXM contact transaction by ID** (Delete). Delete Contact Transaction. Delete a specific transaction. Required: id, directory_id. id is the transactionId. OAuth scope: write:contact_transactions.
- **Get single Qualtrics CoreXM contact transaction by ID** (Get). Get Contact Transaction. Retrieve information about a specific transaction. A transaction is additional data that can be embedded into a user's contact. For example, it could be an actual transaction, like a sales from your sales order system, or other information on the customer from Salesforce. Required: id, directory_id. id is the transactionId. OAuth scope: read:contact_transactions.
- **List all Qualtrics CoreXM contact transactions** (List). List Contact Transactions. Page through all the transactions for the specified contact. To interact with the rest of the Contact Transaction API, you will need the Transaction ID you find for individual transactions you find in the results of this call. Required: directory_id, contact_id. OAuth scope: read:contact_transactions.
- **Update a Qualtrics CoreXM contact transaction by ID** (Update). Update Contact Transaction. Revise information about a specific contact transaction. When you make this call, you are replacing all the contact transaction data. All key-value pairs specified in the data object will completely overwrite the existing key-value pairs in a transaction. This API overwrites Embedded Data When you make this call, you are replacing all the contact transaction data. Body fields: transactionDate, data. Required: id, directory_id. id is the transactionId. OAuth scope: read:contact_transactions.
- **Create a Qualtrics CoreXM contact** (Create). Create Directory Contact. Create a single contact in a specific directory. This API call is only available to XM Directory users. Body fields: firstName, lastName, email, phone, extRef, embeddedData, language, unsubscribed. Required: directory_id. OAuth scope: write:directory_contacts.
- **Delete a Qualtrics CoreXM contact by ID** (Delete). Delete Directory Contact. Delete a single contact from a specfic directory. This API call is only available to XM Directory users. Required: id, directory_id. id is the contactId. OAuth scope: write:directory_contacts.
- **Get single Qualtrics CoreXM contact by ID** (Get). Get Directory Contact. Retrieve a single contact from a specific directory. This API call is only available to XM Directory users. Required: id, directory_id. id is the contactId. OAuth scope: read:directory_contacts.
- **List all Qualtrics CoreXM contacts** (List). List Directory Contacts. Retrieve the contacts in a specific directory. For the last page of results, the value associated with nextPage will be null. This API call is only available to XM Directory users. This API call is not available for XMD Lite Directories Required: directory_id. OAuth scope: read:directory_contacts.
- **Qualtrics CoreXM contacts search** (Search). Search Directory Contacts. Retrieve contacts that satisfy conditions you have specified. You can get the _next page_ of contacts for the filter object by adding the skipToken value returned in the last request to your query params. If the pageSize is set to 10 and all of the 10 contacts in the previous response were the only contacts that satisfied the specified filter, then the subsequent response when the API call is made with skipToken in previous response will return zero contacts. Body fields: filter. Required: directory_id. OAuth scope: read:directory_contacts.
- **Update a Qualtrics CoreXM contact by ID** (Update). Update Directory Contact. Update a single contact in a specific directory. This API call is only available to XM Directory users. Body fields: firstName, lastName, email, phone, extRef, embeddedData, language, unsubscribed. Required: id, directory_id. id is the contactId. OAuth scope: write:directory_contacts.
- **Qualtrics CoreXM customer data request files download** (Download). Retrieve Customer Data via a File. Download file and return data to the customer. Returns the file content. Required: customer_data_request_id, file_id.
- **Create a Qualtrics CoreXM customer data request** (Create). Create Request to Start a Job to Retrieve Customer Data. Create an asynchronous job to fetch customer data. Body fields: operation, emails. Required: operation, emails.
- **List all Qualtrics CoreXM customer data requests** (List). Retrieve Progress for a Data Access Job. Retrieve progress for a particular data access job. Required: customer_data_request_id.
- **List all Qualtrics CoreXM directories** (List). List Directories for a Brand. Using this API, the client can retrieve a list of directories with summary information for each directory. OAuth scope: read:directories.
- **List all Qualtrics CoreXM distribution history** (List). List Distribution History. Return a list showing the distribution history for a specific distribution. Supported Only on XMD This API is only supported for users on XM Directory, not Genesis Contacts. Required: distribution_id. OAuth scope: read:distributions.
- **List all Qualtrics CoreXM distribution links** (List). List Distribution Links. Returns a list of individual distribution links for an existing distribution. Email Status Always Returns "Not Sent" This API call always returns an email status of “Email not sent” and does not report respondent progress. It is intended only to retrieve distribution links that were generated (but not sent) using the Create Distribution API. Required: distribution_id, surveyId. OAuth scope: read:distributions.
- **Create a Qualtrics CoreXM distribution reminder** (Create). Create Reminder Distribution. Create a reminder distribution. Distribution Embedded Data Values specified in the embeddedData parameter may be used within Distribution Reporting as a method of tagging distributions with certain values. These values are not available within the Survey Flow. Body fields: message, header, embeddedData, sendDate. Required: distribution_id, message, header, sendDate. OAuth scope: write:distributions.
- **Create a Qualtrics CoreXM distribution sm** (Create). Create New Survey Distribution via SMS. Returns SMS distribution info. This API uses a 16-second timeout instead of the default timeout. Body fields: sendDate, method, surveyId, name, recipients, message, parentDistributionId, surveyLinkExpirationDate. Required: sendDate, method, surveyId, name. OAuth scope: write:distributions.
- ...and 213 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
