Exporting Form Submissions to CSV via POST
This non-REST-compliant endpoint is provided for use with Project Managed Encryption. In every respect, it behaves identically to the GET endpoint described in the previous section, except that it works over POST. This is necessary because for browser-based applications, it is a dangerous idea to simply link the user to /submissions.csv.zip?2=supersecretpassphrase because the browser will remember this route in its history and thus the passphrase will become exposed. This is especially dangerous as there are techniques for quickly learning browser-visited URLs of any arbitrary domain.
You can exclude the media attachments from the ZIP file by specifying ?attachments=false.
And so, for this POST version of the Submission CSV export endpoint, the passphrases may be provided via POST body rather than querystring. Two formats are supported: form URL encoding (application/x-www-form-urlencoded) and JSON. In either case, the keys should be the keyIds and the values should be the passphrases, as with the GET version above.
Path parameters
The numeric ID of the Project
The xmlFormId of the Form being referenced.
Query parameters
Set to false to exclude media attachments from the export.
If provided, will filter responses to those matching the given OData query. Only certain fields are available to reference. The operators lt, le, eq, neq, ge, gt, not, and, and or are supported, and the built-in functions now, year, month, day, hour, minute, second.
Set to false to remove group path prefixes from field header names (eg instanceID instead of meta-instanceID). This behavior mimics a similar behavior in ODK Briefcase.
Set to true to restore all fields previously deleted from this form for this export. All known fields and data for those fields will be merged and exported.
Set to true to create a boolean column for every known select multiple option in the export. The option name is in the field header, and a 0 or a 1 will be present in each cell indicating whether that option was checked for that row. This behavior mimics a similar behavior in ODK Briefcase.
Response
OK