Load survey responses from the 2ask OData v4 feed into Power BI Desktop, and refresh them in the Power BI service.
The feed is one URL per project. It returns flat rows for closed questionnaires. Choice questions are returned as codes. The labels for those codes are a separate table.
You need an API key. Create it in 2ask under My Account → Manage Settings → API. See Getting started.
Admin API keys must include the scope <obj>responses:read</obj>. To look up the project id from the API, the key also needs <obj>project:read</obj>.
The <obj>project id</obj> is the encoded id from <obj>GET /external/api/v1/projects, for example 60VKN8Z6HZD34</obj>.
Calls count toward the API request limit (by default 60 per minute and 600 per day). A refresh walks one request per page. See Request limit.
Use this URL as the OData service root. Keep the trailing slash.
<obj>https://dc.2ask.com/external/api/v1/projects/{project_id}/responses/odata/</obj>
Other clients send the key as a bearer token:
<code-block>
curl -H "Authorization: Bearer YOUR_API_KEY" \
"https://dc.2ask.com/external/api/v1/projects/{project_id}/responses/odata/"
</code-block>
A successful call returns a service document with three entity sets: <obj>Responses</obj>, <obj>PretestResponses</obj>, and <obj>ValueLabels</obj>.
Admin keys look like <obj>ak_<prefix>:<suffix></obj> and already contain a colon. Put the whole key in the user name. The password is still empty.
Store the key only in the Power BI credential dialog. Do not put it in the URL. Regenerating the key in 2ask invalidates this credential.
| Entity set | Contents |
|---|---|
| <obj>Responses</obj> | Closed live responses for the project. One row per questionnaire. |
| <obj>PretestResponses</obj> | Closed pretest and preview sessions. Same columns as Responses. |
| <obj>ValueLabels</obj> | Labels for coded choices: export_key, coding, label. |
<obj>$metadata</obj> on the same service root describes the columns of this project. The column set follows the survey export schema. After you add, remove, or rename a question, refresh the Power BI model so it picks up the new metadata.
The row key is <obj>survey_session_id</obj>. Question columns use the export key. Characters that are not letters, digits, or _ are replaced with _. A name that starts with a digit is prefixed with _.
Choice values in <obj>Responses</obj> are codes. <obj>ValueLabels</obj> maps each code to its label for the requested locale.
<obj>export_key</obj> is the response column name. <obj>coding</obj> is the code stored in that column. <obj>label</obj> is the answer text.
In Power BI, create a relationship or a merge from the question column to <obj>ValueLabels[coding]</obj>, restricted to the matching <obj>export_key</obj>.
Labels default to the survey’s default language. To request another language, add the BCP 47 query parameter locale to the service root:
<obj>https://dc.2ask.com/external/api/v1/projects/{project_id}/responses/odata/?locale=de</obj>
locale applies to ValueLabels and to column labels in $metadata. It does not change stored answer codes.
<obj>Responses</obj> and <obj>PretestResponses</obj> contain closed sessions only. Open sessions are omitted.
The feed does not apply report filters (filter_ids) and does not include respondent file uploads.
The service returns 100 rows per request. <obj>$top</obj> raises the page size up to 250. Larger values are rejected.
Further pages are linked with <obj>@odata.nextLink</obj> and <obj>$skiptoken</obj>. Power BI follows these links during refresh. Each page is one API request.
The only <obj>$filter</obj> the service accepts is a range on <obj>ClosedAt</obj>, with <obj>ge</obj> and <obj>le</obj> and an ISO-8601 UTC timestamp:
<obj>ClosedAt ge 2026-01-01T00:00:00Z and ClosedAt le 2026-12-31T23:59:59Z </obj>
Each row exposes that timestamp as <obj>closed_at</obj>. Any other <obj>$filter</obj> returns HTTP 400 with the message <obj>Only $filter on ClosedAt ge/le is supported.</obj> When a refresh fails with that message, Power BI has folded a column filter into <obj>$filter</obj>. Load the entity set first, then filter in Power Query with a step that stops query folding (for example <obj>Table.Buffer</obj>) before the filter step.
<obj>$orderby</obj>, <obj>$skip</obj>, and <obj>$expand</obj> are not available on this feed.
When the limit is reached, the service returns HTTP 429. For a large survey, schedule the refresh outside other API jobs that use the same key, and avoid refreshing <obj>Responses</obj> and <obj>PretestResponses</obj> more often than you need.
Publish the report, then open Settings → Datasets → Data source credentials (or Gateway connection / Cloud connection, depending on the workspace). Set the credentials to Basic, with the same API key as the user name.
The feed is served over public HTTPS, so an on-premises gateway is not required for this source.
Scheduled refresh uses the same paging and the same request limit as an interactive load.