Authenticate to the Qualtrics API using either a static API token or OAuth2 client-credentials, and target the correct datacenter
domain: api.qualtrics.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Find your account's datacenter ID under Account Settings > Qualtrics IDs -- every API call must go to https://{datacenterId}.qualtrics.com/API/v3/... not a generic qualtrics.com host
For simple token auth, generate an API token from Account Settings > Qualtrics IDs and send it on every request as the X-API-TOKEN header
For OAuth2, create an OAuth client in the OAuth Client Manager with grant type Client Credentials, noting the Client ID and Client Secret
Request an access token from the datacenter's OAuth token endpoint using the client credentials grant
Send the resulting bearer token as an Authorization header on subsequent v3 API calls instead of X-API-TOKEN
Store whichever credential you choose securely and rotate the API token or client secret if it may have been exposed
Known gotchas
Using the wrong datacenter subdomain (or a generic one) causes requests to fail even with valid credentials -- the datacenter ID is account-specific and not guessable
API token and OAuth client credentials are separate auth mechanisms with different header formats (X-API-TOKEN vs Authorization bearer) -- they are not interchangeable in the same request
OAuth client-credentials tokens are scoped and expire, so long-running integrations need a refresh/re-request cycle, unlike a long-lived static API token
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?