Get Respondent Encoded ID

In order to allow more flexibility with respondent IDs, we have implemented a new layer, that means respondent IDs no longer need to be restricted to Alpha numeric values.

To do this, there is now an extra step, whereby you will need to request respondent_encoded rather than respondent_id

First we need to request the respondent_encoded. Make sure this request is sent to the below endpoint.

https://public-survey-data-api.rose.conceptsauce.io/api

We place the none alphanumeric respondent id in respondent_id object, plus making sure we use the right survey_id.

{
	"event_type": "respondent_encoded",
	"action": "get_respondent_encoded",
	"data": {
		"survey_id": "SURVD01GA3B5TJA3CBKZQG78JARZDC5",
		"respondent_id": "ter_a.gun_MLshow_7_2_52_14_265-"
	}
}

As you can see, we have used a none standard and not restricted to alpha numeric value respondent_id: ter_a.gun_MLshow_7_2_52_14_265-

The response will give you the respondend_encoded.

{
	"reason": null,
	"code": 200,
	"data": {
		"survey_id": "SURVD01GA3B5TJA3CBKZQG78JARZDC5",
		"respondent_id": "ter_a.gun_MLshow_7_2_52_14_265-",
		"respondent_encoded": "enc1ffce6769606f5fb48349db62d98f8830cbe6cdb"
	},
	"event_type": "respondent_encoded",
	"action": "get_respondent_encoded",
	"client_msg_id": "",
	"platform_status": {
		"status": "running",
		"shut_down_timestamp": 0
	}
}

Now you can use this respondent_encoded in all the other API requests.