> ## Documentation Index
> Fetch the complete documentation index at: https://docs.repdata.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Environments & Status Codes

> Staging and production environments, recommended test surveys, and the supplier-facing status codes and parameters returned on redirects.

## Environments

Research Desk provides two environments for integration work:

* **Staging** `https://stage-api.researchdesk.com` — Use this for all development and testing. It mirrors production behavior without real respondent traffic.
* **Production** `https://api.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.

### Staging Test Surveys

To ensure successful end-to-end testing, we recommend using the following surveys in the staging environment during integration:

| Survey Number | Description                                                                                |
| ------------- | ------------------------------------------------------------------------------------------ |
| `2634`        | Short, 1-question survey for testing disposition codes. Wait 30 seconds before completing. |
| `2635`        | Longer, \~10-minute survey.                                                                |

<Tip>
  Once you're ready to conduct a live fielding test, contact Rep Data's Supply team at [supply@repdata.com](mailto:supply@repdata.com).
</Tip>

For the JSON response envelope and HTTP behavior, see [Response Structure](https://docs.repdata.com/supply/overview/03-response-structure).

***

## Respondent Status Codes (isc)

When a respondent is redirected from Research Desk back to your platform, an `isc` (internal status code) is appended to the redirect link. These `isc` codes are supplier-facing and identify the respondent's disposition (complete, terminate, over-quota, security, etc.).

See [Respondent Status Codes](/supply/overview/04-respondent-status-codes) for the full `inbound_code`, `isc`, and `rdThreat` reference.

***

## Redirect Link Parameters

Research Desk automatically appends the following parameters to your redirect links. Use them to reconcile and route respondents.

| Parameter                   | Description                                                                                                           |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| `[%RID%]`                   | The RID value originally shared by the supplier.                                                                      |
| `[%PID%]`                   | The PID value originally shared by the supplier.                                                                      |
| `[%isc%]`                   | The returned `isc` status code.                                                                                       |
| `[%TermedQuotaID%]`         | The Quota ID(s) a respondent termed on. Returns only on `SurveyOverquotaLink` when `ISC=6002`.                        |
| `[%TermedQualificationID%]` | The Qualification ID(s) a respondent termed on (e.g. `42` for Age). Returns only on `SurveyTermLink` when `ISC=5003`. |
| `[%rd_st_id%]`              | The Stream ID (number). Available for all statuses.                                                                   |
| `[%rd_sur_id%]`             | The Survey ID (number). Available for all statuses.                                                                   |

In addition, Research Desk appends a hashed key (`hk`) for secure redirects and `SCPI` (the respondent's CPI on Stream entry). See [Secure Redirects: Link Hashing](https://docs.repdata.com/supply/guides/04-secure-redirects) for details on the `hk` value.