Loading documentation…
{{ error }}
Exports
Download event data for reports and offline workflows.
Export event data
Use HTTP GET on your authorized organizer origin, with the event UUID before each path. Exports return file bytes and follow the organizer's current export columns and permission checks.
| Data | CSV path after the event UUID | Excel path |
|---|---|---|
| Orders | /orders/export_to/csv |
/orders/exportexcel |
| Attendees | /order_lines/export_to/csv |
/order_lines/exportexcel |
| Waiting list | /waitinglists/export_to/csv |
/waitinglists/exportexcel |
| Check-ins | /acs/export_to/csv |
Use CSV. |
| No-shows | /acs/noshow_export_to/csv |
Use CSV. |
exportexcel produces XLSX. The Exports reference includes binary response schemas and download examples in cURL, PHP, Node.js and Python. Save the bytes instead of calling a JSON parser.
Validate downloads
Check HTTP status, Content-Type and Content-Disposition. Access failures can redirect or return HTML. Keep automatic redirect following disabled and reject unexpected content types so an organizer error page is not saved as a spreadsheet.
Protect exported data
Exports contain personal data. Limit organizer access, store downloads securely and apply the retention policy in privacy and data handling. For continuous record updates, use the JSON reads under Orders and Attendees and the integration guide.
Attachment uploads and invoice/ticket PDF downloads are covered in Files.