Implement SurveyMonkey OAuth authorization and request the correct API scopes for a third-party app
domain: developer.surveymonkey.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an app in the SurveyMonkey Developer Portal and configure a redirect URI
Choose which scopes your app needs (e.g. surveys read/write, responses read/write, collectors, webhooks) and mark each as required or optional
Redirect the user to the SurveyMonkey OAuth authorize URL with your client_id, redirect_uri, and requested scopes
Exchange the returned authorization code for an access token via the token endpoint using your client_id/client_secret
Store the access token and use it as a Bearer token on subsequent api.surveymonkey.com/v3 requests
Handle the case where a user declines optional scopes by checking granted scopes before calling scope-gated endpoints
Known gotchas
The Create/Modify Surveys and Create/Modify Responses scopes require explicit SurveyMonkey approval before they can be used in a public (non-private) app
Some scopes only function correctly if the authorizing user's SurveyMonkey account is on a paid plan -- calls can fail for free-tier users even with the scope granted
Access tokens are tied to the authorizing user's account, not the app, so a token only works for that user's surveys and collectors
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?