Authenticate to the Alchemer (formerly SurveyGizmo) REST API and retrieve survey responses
domain: apihelp.alchemer.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an API Token and API Token Secret from your Alchemer account (or use basic auth with your login credentials as an alternative)
Include the token/secret as query parameters (or use basic auth headers) on every request to the Alchemer REST API base URL
Call GET /survey/{surveyId}/surveyresponse to list responses for a given survey, excluding deleted responses by default
Apply filter parameters on the GET request (Alchemer supports filtering only on GET, not on PUT/POST/DELETE) to narrow by date range or status
Call GET /survey/{surveyId}/surveyresponse/{responseId} to fetch a single response's full detail when needed
Page through results using the page parameter/response metadata for surveys with large response volumes
Known gotchas
Filtering is only supported on GET (list/read) calls -- you cannot filter which records a PUT/POST/DELETE affects, so those must target a specific response ID
At least one data parameter must be included when creating or updating a response via POST/PUT, even though no single specific field is mandatory
Deleted responses are excluded from the default list endpoint, which can make response counts appear lower than the survey's reported total
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?