The previous site was hosted by Stoplight; this new site is self-hosted and will remain so going forward.

What's the same​

All content has moved as-is. If you used the old site, you'll find everything you expect:

• The complete Public API reference — all 321 endpoints across 46 OpenAPI specs, rendered with interactive try-it panels and code samples in multiple languages.
• The full Extension SDK documentation — guides for every plugin type, the XMT CLI reference, and the manifest specification.

The URL structure is preserved wherever possible, and 301 redirects are in place for any paths that changed. If you have a bookmark that doesn't redirect correctly, let us know.

What's new​

The two most significant changes are unified navigation and full-site search.

Unified navigation. Extension SDK and Public API docs now live under one roof with a shared top nav and a single place to bookmark. Previously, the two sets were hosted separately with no cross-linking.

Faster search. Press Cmd+K (or Ctrl+K) from anywhere on the site to search across both documentation sets simultaneously. The search index is built at compile time, so results are instant with no external service dependency.

Also new:

• Dark mode — toggle between light and dark themes using the button in the top-right corner.
• This blog — release notes, tutorials, and platform updates will be published here going forward. Subscribe via RSS or Atom using /blog/rss.xml and /blog/atom.xml in your feed reader.

How to use it​

The site has two primary sections reachable from the top nav:

The sidebar on each section mirrors the structure you already know. The API reference pages include the full parameter and response schema on the left, with request/response examples on the right. New to extensions? Start with Get Started with the Extension SDK.

Feedback​

If you find broken links, missing content, or anything that worked better before, use the feedback icon at the bottom of any page to submit a response.

Purpose-Built Apps are generally available​

As of January 2026, Purpose-Built Apps (PBAs) are generally available. The early access gate has been removed from all PBA documentation — if you've been waiting on GA before building production extensions, now is the time.

PBAs let you embed custom web applications directly inside the Qualtrics platform using a plugin-based architecture. They're the right tool when you need a full UI — not just a widget or a step in a workflow — that integrates tightly with Qualtrics data and context.

New in the GA docs:

• Theming. The PBA documentation now includes a complete section on applying Qualtrics-consistent styles to your app using the platform's theming API. Building a UI that matches the host product is now documented with examples.
• Translations. The translations section has been expanded with more detail on how to structure locale files, register translations at init time, and handle fallback behavior when a translation key is missing.

Full documentation: Extension SDK → Purpose-Built App.

fetch3: the new standard for external requests​

The Plugin Client now includes a fetch3 method, which replaces fetch2 as the recommended API for making requests to external services from within a plugin.

pluginClient
  .fetch3('https://api.example.com/data?filter=active', {
    method: 'GET',
    connection: {
      connectionName: 'my-service',
      paramFormat: 'header',
      paramName: 'Authorization',
      paramTemplate: 'Bearer %s',
    },
  })
  .then(({ data, status }) => {
    console.log(status, data)
  })

Key improvements over fetch2:

• All content types supported. Pass FormData directly in the request body for file uploads. Binary responses (images, PDFs, etc.) are returned as ArrayBuffer automatically.
• Auto-decoded responses. The response data field is decoded based on the Content-Type header — JSON becomes a parsed object, text becomes a string, binary becomes an ArrayBuffer. No manual parsing.
• Automatic credential refresh. If the destination server returns a 401 or 403 due to an expired credential, fetch3 retries the request with a refreshed credential automatically.
• Query params in the URL. Include query parameters directly in the URL string rather than in a separate params object.

fetch2 continues to work and has no announced removal timeline — migrating is not urgent. That said, fetch3 is the right choice for new integrations and any existing code paths that handle file uploads or binary responses.

fetch3 requires @qualtrics/plugin-client version 1.10.4 or greater. Full reference: Extension SDK → Plugin Client → fetch3.

XM Solutions: Overview resource type​

XM Solutions are extensions that embed a structured, multi-resource experience directly inside Qualtrics — guided workflows, dashboards, or onboarding flows built on Qualtrics data. Each solution is made up of individual resource pages that users navigate through.

XM Solutions now support a new Overview resource type. An Overview resource renders as a dedicated landing page at the start of the solution, before the user reaches any individual resources. Use it to introduce the solution's purpose, explain prerequisites, or surface context that applies across all resources.

If your XM Solution has multiple resources that share common setup steps or require orientation to use effectively, an Overview resource is the right place to put that content. See Extension SDK → XM Solution → Overview Page for the full reference.

Theme sharing between Purpose-Built Apps and Custom Blocks​

The Purpose-Built App documentation now covers how to share your PBA's active theme with embedded Custom Block plugins. When a Custom Block is displayed inside a PBA, you can pass the PBA's theme — colors and visual configuration — down to the Custom Block using the getTheme function from the Custom Block SDK. This keeps the UI consistent across the full app without manually syncing theme values between plugins.

See Extension SDK → Purpose-Built App → Sharing Themes With Custom Blocks for the updated section.

Questions about any of these updates? Ask in the Developer Corner on the Qualtrics Community.

Response Imports/Exports API is back​

If you're building an ETL pipeline, backup workflow, or third-party analytics integration that pulls response data out of Qualtrics in bulk, the Response Imports/Exports API is the right endpoint set to use. It covers exporting response files, triggering response imports, and checking import job status.

This spec is now available in the Public API reference. The documentation had been removed about three years ago; it's been restored following a recent audit that confirmed the endpoints are stable and production-ready. Navigate to Public API → Response Imports & Exports in the sidebar to browse the full spec.

Full API reference coverage​

If you've been working off incomplete third-party references or discovering endpoints by trial and error, the documentation now covers the complete Qualtrics Public API surface. All 321 endpoints across 46 OpenAPI spec files are included, spanning:

• Surveys and survey definitions
• Contacts and directory management
• Event subscriptions
• Audit logs
• GDPR and CCPA compliance endpoints
• Response exports (now restored, above)

Browse the full reference from the Public API introduction, or open Public API in the site nav.

Staying current​

API reference documentation is generated directly from the OpenAPI specs maintained by the owning engineering teams. New endpoints and parameter changes will appear in the reference as specs are updated upstream. Start with the Qualtrics API Quick Start if you are new to the APIs.

Subscribe via /blog/rss.xml or check back here for future update summaries. If you notice a missing endpoint or a spec that looks out of date, use the feedback icon at the bottom of any page.