# SurveyMonkey setup for PopMCP You end up with the Access Token from a Private app registered in the SurveyMonkey developer portal, plus your account's data region (us, eu or ca), pasted into PopMCP. - Auth: API credentials - Setup time: 6 min - API base URL: https://api.surveymonkey.com/v3 - Credentials screen: https://developer.surveymonkey.com/apps/ - Provider docs: https://developer.surveymonkey.com/api/v3/#getting-started ## Approval required before this works A SurveyMonkey app runs in draft mode for only 90 days; to keep it alive for your own team you must deploy it as a private app, and SurveyMonkey's help centre states an Enterprise plan is required to deploy a private app. A public app - one any SurveyMonkey account can connect - must additionally be reviewed and approved by SurveyMonkey. - Typical wait: None to start (draft app credentials work immediately); Enterprise is a sales conversation, and public app review is not given a published SLA - Cost: No fee for the developer app or the review itself. The gate is the plan: SurveyMonkey's help centre states "An Enterprise plan is required to deploy a private app", and Enterprise is quote-only (contact sales). SurveyMonkey publishes no API price list, so treat any specific per-seat figure you see quoted elsewhere as unverified. - Blocked until approved: After the 90-day draft window an undeployed app is disabled and its tokens stop working. Draft apps are capped at 120 requests/minute and 500 requests/day, and are usable only from the SurveyMonkey account the app is registered to, so you cannot connect a client's or colleague's account. Deploying private removes the review requirement ("Private apps don't need to be reviewed by SurveyMonkey") but gates you behind Enterprise, and every user must be a logged-in member of the SurveyMonkey team the app is registered to on a paid plan that offers direct API access. Public apps instead need SurveyMonkey sign-off, and the Create/Modify Responses and Create/Modify Surveys scopes require explicit approval; View Response Details and Create/Modify Collectors additionally require the connecting user to be on a paid plan. - Works meanwhile: Register a draft app at the SurveyMonkey developer portal and get a client ID, secret and access token instantly. Reading surveys, collectors and responses on your own account works right away within the 500/day draft limit, which is enough to build and test the whole integration. ## Before you begin - A SurveyMonkey account. Anyone can register a draft app, whose access token queries their own account for 90 days - A paid SurveyMonkey plan offering direct API access, needed to deploy the app as Private before the draft window ends - All users of a Private app must belong to the same SurveyMonkey team - A paid plan for unlimited response detail, since Basic plans are capped at 25 responses per survey - Knowledge of whether the account sits on the US, EU or Canada data region ## Get your credentials ### 1. Sign in to the developer portal Go to developer.surveymonkey.com and sign in with the SurveyMonkey login that owns the surveys. Screen: https://developer.surveymonkey.com/apps/ ### 2. Add a new Private app Open the MY APPS tab and click Add a New App. Name it `PopMCP`, select Private App, then click Create App. Screen: https://developer.surveymonkey.com/apps/ ### 3. Tick the scopes the connector needs Open the app's Scopes and mark View Surveys, View Responses and View Response Details as required. Add the create and modify scopes only if the agent should write. ### 4. Copy the Access Token Open the app's Settings and copy the value labelled Access Token. Do not copy the Client ID or Secret. ### 5. Deploy the app as Private Open Deploy and publish the app as a Private App before the 90 day draft window ends. ### 6. Paste the token and region into PopMCP In PopMCP's SurveyMonkey connector paste the value into Access token, set Data region to `us`, `eu` or `ca`, then save. ## Fields PopMCP asks for - Access token (apiKey) [required]: Create an app at developer.surveymonkey.com (My Apps → New app → Private), then copy the Access Token from the app's Settings and paste it here. Tick the scopes you need (View/Create Surveys, View Responses + View Response Details, View/Create Collectors, Contacts, Webhooks). Note: a free/Draft app's token works for 90 days; a deployed Private app (paid plan with API access) gives a token that doesn't expire. Stored encrypted. - Data region (us, eu, or ca) (region): Where your SurveyMonkey account's data is hosted: us (default, api.surveymonkey.com), eu (api.eu.surveymonkey.com), or ca (api.surveymonkey.ca). A token only works against its own region's host. Leave as us unless your account uses EU or Canada data residency; if the connection is rejected, try the other region. ## Verify PopMCP shows the SurveyMonkey connector as Connected, and a test call listing your surveys returns their titles and IDs. ## Troubleshooting ### 401 with "Client authentication failed" Cause: The Client ID or Secret was pasted instead of the Access Token, or the token belongs to a different account. Fix: Copy the value labelled Access Token in the app's Settings and re-paste it. ### The Access Token field is not visible in Settings Cause: The app type is not set to Private. Fix: Change the app type to Private App in the app's Settings, save, then reload the page. ### The connection worked for a while, then stopped Cause: The app was left as a Draft, and a draft app is disabled 90 days after registration. Fix: Deploy the app as a Private app on a plan with direct API access, then re-copy the token into PopMCP. ### Every call 404s or is rejected even with a fresh token Cause: Wrong data region. A token only works against api.surveymonkey.com, api.eu.surveymonkey.com or api.surveymonkey.ca respectively. Fix: Change the Data region field to eu or ca and reconnect. ### "Client revoked access grant" Cause: Someone removed the app's authorisation from the SurveyMonkey account. Fix: Re-authorise the app in the developer portal and copy the token again. ### Only 25 responses come back per survey, or calls fail with error 1005 Cause: The account is on a Basic plan, which caps responses_read_detail at 25 responses per survey. Fix: Upgrade the SurveyMonkey plan for unlimited response access. Nothing changes on the PopMCP side. --- Source: https://www.docs.popmcp.com/docs/integrations/survey-monkey/