Skip to main content
GET
List Survey Rows
← Employees API Retrieve the employees table as one row per mobility survey. There are three kinds of row:
  • response: an answered survey. One row however many commutes the answer holds (the respondent changed address or transport within the period): commute_count, period_ids and the summed co2e. A commute that answers no survey (QR, file upload, older data) is a response row of its own.
  • pending: a survey sent and not answered yet. Sending the same survey again (same employee, period and template) updates this row instead of adding one.
  • employee: a person with no response and no pending survey.

Request

Headers

string
required
Your API key for authentication
string
required
Your organization UUID

Query Parameters

It takes the same perimeter, search and column filters as List Employees (V2): consolidate_group, organization_id[], filter_by, filter_match, filter_or_fields, plus page and size. filter_by applies to the row columns below; period_date:rd[from,to] keeps the rows whose period lies in the range.
string
Sort as field:asc$other:desc. Rows then follow the newest created, then the newest updated.Fields: email, name, organization_name, start_date, end_date, status, response_medium, survey_template_name, sent_at, send_count, responded_at, created_at, updated_at, co2e, commuting_type, transport_type, fuel_type, total_km, daily_trips, hours_worked_per_day, carpoolExample: sort_by=sent_at:desc

Response

array[object]
integer
Total rows matching the filters
string
Hash of the filters, required by the bulk actions over every matching row: POST /v2/employees/survey-rows/delete-preview, /delete (with delete_orphan_employees), /resend-preview and /resend (with only_pending). They need write permission.