Staging
We currently use a staging environment to allow developers to set up their integration in a risk free manor. The environment is free and fully functional. API calls to Staging should use https://api-staging.respondent.io as the base URL.
Participant API developers should build their integration in staging and then switch over to the production environment when they are ready to go live. Learn more here
Production
API calls to Production should use https://api.respondent.io as the base URL.
Requirements for Production Credentials
Before your implementation can get access to production, we require a few steps to ensure that your researcher customers and Respondent participants have a great experience.
Specifically, before releasing production credentials:
- We will conduct end-to-end user testing on Staging to validate that projects can be created and recruited effectively and that participants are statused appropriately.
- We must have an executed API Partner Master Services Agreement (MSA) in place
- You must have a designated Production researcher organization set up on the Respondent platform, with the owner set to be the email address where you want to receive transactional emails
- That designated Production account must be funded with incentives and recruiting fee credits appropriate for the volume of recruiting you intend to conduct
Moving from Staging to Production
Staging and production use different audience parameter IDs
Lookup IDs for industries, skills, topics, and jobTitles differ between staging and production environments.
- It is important to note that lookup IDs for industries, skills, topics, and jobTitles differ between staging and production environments and these IDs will need to be updated when moving to your production environment.
- Additionally when switching to production, all projects will be paused by default and will need be un-paused to recruit from our panel. This allows for internal Production testing and that automatic pause can be removed at your request.
- For internal Production testing, you can invite specific internal participants into a Paused project using the Share link provided for each project. That link can be found by clicking into the project on the Respondent platform and selecting the "Share" dropdown in the upper right of the project page. This will allow any participant with that link to access the project even though it is paused, but participants will still need a real participant account and match the demographic filter criteria for the project.
- Any webhooks will need to be re-established using the Production API endpoints for webhook creation