Staging
The Staging environment is free to use and fully functional, allowing developers to build and test integrations in a risk-free environment. To learn more, see: Staging Environment- Base URL: https://api-staging.respondent.io
Production
Once your integration is ready, switch to the Production environment. To request access, see: Moving to production- Base URL: https://api.respondent.io
What changes when you move to production
Staging and production are completely separate environments, and nothing is copied from one to the other. Plan for the following when you migrate your integration.Accounts, credentials and webhooks
Researcher accounts, organizations, teams and API credentials from staging do not exist in production. Set them up again by following Moving to production, even if you use the same email addresses. Webhooks don’t carry over either. Register your production webhook with your production credentials. See Webhooks.Lookup IDs
Lookup IDs for industries, skills, topics and job titles are different in production. Look them up again with your production credentials and update any IDs your integration stores or sends.Published projects start paused
In production, a project you publish through the API starts with itsprojectRecruitingStatus set to PAUSED, so you can test it before it recruits. Staging doesn’t do this. See Test your live integration in production.
Test participants
POST /v1/profiles is only available in staging. In production, test with your own people through the project’s invite link. See Test your live integration in production.