Set Up Saved Credentials

Saved credentials let Domandata features use outside services without asking you to paste a secret every time: AI models, voice, participant emails and texts, Prolific and CloudResearch Connect recruitment, and the OSF, Harvard Dataverse, and Zenodo repositories. They all live in one place: Settings → Integrations → API Keys.

Saved credentials are different from Domandata API keys. Domandata API keys, listed first in the same API Keys section under Your Domandata Keys, let outside scripts pull response data from Domandata; each is shown once when you create it and stored only as a hash. Saved credentials let Domandata call another provider on your behalf.

1. Step 1: Open Settings → Integrations. Go to Settings from the app navigation and choose the Integrations tab. (Older links to the MCP tab open it too.)

   Step 1: Open Settings

2. Step 2: Open API Keys and find the kind of key. Keys are grouped into AI, Voice & Video (AI Model, Voice, Video Avatar), Participant Messages (Email through Resend, Text Messages through Twilio), Recruitment (Prolific, CloudResearch Connect), and Research Repositories (OSF, Harvard Dataverse, Zenodo). Each one says what Domandata uses it for and links to the page where the provider issues keys.

3. Step 3: Add the key. Each service is one line showing its status (Not set up, 2 saved, Connected, or Needs attention); services you already use start open. Click a service to open it, then click Add Key (or Add Token, or Connect for a repository). Paste the key or token into its field: it stays hidden as you type (use the eye button to check it), and your browser won't offer to save it as a password, since it isn't your Domandata login.

4. Step 4: Name it. Use a name that explains the owner and purpose, such as Lab OpenAI key - pilot testing or Twilio reminders - Fall panel. AI Model, Voice, Email, and Text Message keys also take their provider settings (endpoint, model, sender address or number); a Video Avatar key takes only its provider. Prolific, Connect, and repository tokens are checked with the provider before they are saved, so a mistyped token is caught right away.

5. Step 5: Share it with your team, if you want. In a shared team workspace, AI Model, Voice, Video Avatar, Email, and Text Message keys can be saved for the team so every member can pick them. Choose this when you add the key. Prolific and Connect keys are always personal, because they carry your account's spending rights, and repository tokens belong to your own account.

6. Step 6: Use it in the feature. Return to the survey feature that needs the key and choose it from Use saved key. When nothing is saved yet, that spot links to Settings → Integrations. You can also still paste a key directly into a Text Chat or Audio Conversation question, or save a Prolific or Connect key from Deploy → Recruitment; those keys show up here too.

   Step 6: Use In Export

• See where a key is used. Each key shows how many surveys use it. Click Used in … surveys to list them, with where each one uses it (a question, Silicon Sample, a Prolific study, a Connect project) and a link to the survey. Email and text-message keys are picked each time you send, so they show that instead of a count.
• Edit or rename. The pencil button edits a key's name and provider settings. For Prolific and Connect keys it renames the key; the token itself stays as saved.
• Replace (rotate) a key. The replace button swaps in a new secret while keeping the same saved key, so every survey, question, and running Prolific study or Connect project that uses it keeps working. Use it when a provider key is rotated, expires, or may have been exposed. A key marked Re-enter key needs its secret pasted again before it can be used.
• Delete or disconnect. The delete button removes the key from Domandata after you confirm, and lists the surveys that use it first. If a Prolific study or Connect project is live with that key, Domandata names the survey and asks again, because deleting the key stops automatic approval and pausing there. Deleting a key here never changes anything in your Prolific, Connect, or repository account.

• Audio Conversation questions: use a Voice credential for a speech provider (ElevenLabs, Gemini, Hume, or OpenAI-compatible). It stores the provider plus optional transcription and speech endpoints, models, and a voice; blank fields use the provider defaults. A key pasted into the question is saved here automatically. The OpenAI Realtime provider uses an OpenAI-compatible Voice key or an AI key. Audio Response transcription accepts the same Voice keys.
• Video Conversation questions: use a Video Avatar credential holding an Anam API key. A key pasted into the question is saved here automatically. The key never leaves Domandata's server: each call gets a short-lived, single-call session instead. See Video Conversation Survey Questions.
• Text Chat questions: use an approved AI credential that matches the model and privacy requirements for respondent-facing conversations.
• Silicon Samples: use an AI credential intended for synthetic dry runs, and separate it from production research workflows when possible.
• Email or SMS sending: use provider credentials owned by the team responsible for participant communications.
• OSF Registrations: use a token that can read the private draft registration you need to confirm. Domandata does not create OSF Projects or upload files to OSF.
• Harvard Dataverse: use a token from the account that should own or edit the replication dataset.
• Zenodo: use a personal access token with the deposit:write and deposit:actions scopes.
• Prolific and CloudResearch Connect: use the token or key from the researcher account that should pay for studies. Save more than one (for example, one per grant) and pick the one to use on each survey's Deploy → Recruitment card.

• Store provider secrets only in Settings → Integrations, never in survey text, code, or public documentation.
• Use one credential per service, team, or workflow so access can be revoked cleanly.
• Rotate credentials with Replace when a teammate leaves, a project ends, or a secret may have been exposed; surveys that use the key keep working.
• Delete credentials that show Not used in a survey and that no export or integration still needs.
• Confirm cost and usage limits with the provider before running large AI, email, or SMS jobs.

• Pull Survey Responses With the API
• Preregister and Archive a Domandata Study
• Deposit a Replication Package in Harvard Dataverse
• Generate and Clean Up Silicon Samples
• Text Chat Survey Questions