Environments & Status Codes

Environments

Research Desk provides two environments for integration work:

Staging https://stage-demand.researchdesk.com) — Use this for all development and testing. It mirrors production behavior without real respondent traffic.
Production https://demand.researchdesk.com) — Your live environment once integration testing is complete.

We strongly recommend completing full end-to-end testing in the staging environment before going live. This includes testing both complete and terminate survey paths in an incognito browser window to avoid triggering Research Defender’s security flags during QA. Respondent outcomes on survey redirects use inbound_code values (complete, terminate, security, over-quota). See Respondent Status Codes for the full code reference.

API Responses

All endpoints return JSON-encoded responses and standard HTTP status codes. Error messages are designed to be displayed to end users. Error response examples: Response (400):

{
    "message": "Survey name is required."
}

Response (404):

{
    "message": "Survey could not be found."
}

Response (405):

{
    "message": "Survey objects cannot be deleted."
}

Response (500):

{
    "message": "Our server experienced an unexpected error."
}

Overview

Integration Guide

API Reference (v1)

Environments

API Responses

​Environments

​API Responses

Environments

API Responses