curl --request GET \
--url https://app.usertick.com/api/public/v1/surveys/{surveyId}/results \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.usertick.com/api/public/v1/surveys/{surveyId}/results', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.usertick.com/api/public/v1/surveys/{surveyId}/results"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)Get a survey's results per question
A survey’s results as the Results page in Usertick reads them, per question: answered, counts per option or value, averages, NPS with promoters, passives and detractors, CSAT, rankings, matrix rows, ranges, this-or-that pairs, timing, the series over time and the window before (vs previous), with the summary and where responses came from. It takes the Results filters within the plan’s response history (window.from says where the read starts). A filter past its bound is 400, never shortened: an unknown time zone is 400 PUB-001-004. Written answers, contact details and files are left out: they are responses, read with responses:read (GET /responses?surveyId=). partial is true when part of the read failed.
Scopes: analytics:read.
curl --request GET \
--url https://app.usertick.com/api/public/v1/surveys/{surveyId}/results \
--header 'Authorization: Bearer <token>'const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://app.usertick.com/api/public/v1/surveys/{surveyId}/results', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://app.usertick.com/api/public/v1/surveys/{surveyId}/results"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)Authorizations
Query Parameters
Response
The results.
A survey's results as aggregates. Written answers, contact details and files are responses, read with responses:read.