Create and modify a survey's structure using the Qualtrics survey-definitions API
domain: api.qualtrics.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with an API token (X-API-TOKEN) or OAuth bearer token against your account's datacenter base URL
POST to /API/v3/survey-definitions to create a new blank survey definition and capture the returned SurveyID
Use the blocks and questions sub-resources under /survey-definitions/{surveyId} to add blocks, questions, and flow elements
PUT to /survey-definitions/{surveyId}/metadata to update top-level settings like SurveyName, SurveyStatus, or expiration dates
GET the survey definition back to confirm question ordering, blocks, and flow logic were saved as intended
Activate the survey (setting SurveyStatus appropriately) only after verifying the definition, since some downstream distribution actions require an active survey
Known gotchas
The survey-definitions API is distinct from the surveys/responses read APIs -- building and editing survey structure uses different endpoints than exporting response data
Editing a survey's definition after it has already collected responses can invalidate or shift question mappings in previously exported data
Some fields (like complex branching/logic) require carefully structured nested JSON where the platform's error messages may not clearly identify which nested block failed validation
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?