Skip to main content
Before your integration can move from Staging to Production, please complete the following steps:

​
1. Staging Implementation Review

Provide a comprehensive screen-recording demo of your integration in our Staging environment. We review this demo to confirm that your integration implements the required flows and meets our quality standards. We want to confirm your product can drive the Respondent API end-to-end. Every required action should be demonstrated by:
  1. Triggering it from your product UI — the same surface your end users would see.
  2. Showing the resulting state in your product UI — so we can see your integration handled the response.
  3. Showing the same state change in Respondent’s UI — so we can confirm the API call had the intended downstream effect.
For step-by-step instructions on what to record and how to submit, see the Demo video checklist.

​
Recording your demo

  • Tool — any screen recorder is fine (Loom, QuickTime, OBS, Drive upload). Narration is encouraged but not required.
  • Test participants — seed participants in staging via POST /v1/profiles; see Staging Environment. You can sign in as those participants here to apply to your own project and reply to messages.
  • Some items don’t need video — confirming auto-pay is on, listing which study types and screener question types your integration supports, and sharing your staging organization, team, and project IDs can all go in the email body. We’ll cross-check against your staging org.
  • Token hygiene — keep API tokens and secrets off-screen. Staging tokens are still credentials.
Once these flows are validated, you’ll be cleared for Production credentials.

​
2. Execute the API Partner Master Services Agreement (MSA)

  • Review and sign the MSA to formalize our partnership and credits
  • Return the fully executed document to our Sales team.

​
3. Production Organization & Team Setup

  • Create a Production researcher organization and a dedicated team for API projects on Respondent.
    • The email address of the organization owner will also be used to receive transactional emails. Please ensure this address is a shared inbox capable of handling high-volume traffic.
  • Share with us the organization_id, team_id and the owner’s email for us to fund the account with incentives and recruiting fee credits appropriate for the volume of recruiting you intend to conduct.
Questions? Reach out to partnersupport@respondent.io
When migrating your integration, please note the following:
  • Lookup ID Differences: Lookup IDs for industries, skills, topics and jobTitles are different between staging and production. You will need to update these IDs when moving to production
  • Auto-pause of Projects: All newly created production projects will be paused by default. You can request partnersupport@respondent.io to have this removed from your integration once ready
  • Internal Testing in Production: You can test your project by inviting internal participants via the Share link. These are accessible in the Respondent platform by clicking into the project and selecting the “Share” dropdown (top right). Participants must have a valid Respondent account and match the project’s demographic filters
  • Webhook Setup: Webhooks configured in staging do not carry over to production
Last modified on June 26, 2026