Export to Excel
Download a parser's data as a spreadsheet, optionally filtered by processing date.
/dapi/v1/parser/{parser_id}/export/Returns an .xlsx workbook of the parser's entries.
The export endpoint gives finance and operations teams a ready-to-open spreadsheet. It's also a simple way to pull data on a schedule, for example a monthly file for your accounting system.
This endpoint takes the parser ID, not the slug
Open the parser in the dashboard and copy the ID from the address bar: app.simplyparse.com/parsers/<parser_id>.
Download a workbook
Prop
Type
Both are optional. Without them you get every entry.
curl -G "https://api.simplyparse.com/dapi/v1/parser/$PARSER_ID/export/" \
-H "Authorization: Token $SIMPLYPARSE_API_TOKEN" \
-d processed_from=2026-03-01 \
-d processed_to=2026-03-31 \
-o march.xlsxThe trailing slash in /export/ is part of the path. The file name is in the Content-Disposition header, for example Supplier invoices-2026-04-01-09-30.xlsx.
What's in the workbook
One sheet, one header row, and one row per entry. When an entry has a list field such as line items, it is expanded into one row per item. The entry's other values appear on the first of those rows, and the following rows hold only the item columns. Use S.No to group rows back into entries. Nested objects are flattened into dotted columns, for example vendor.name.
The first four columns identify where each row came from:
| Column | Meaning |
|---|---|
S.No | Entry number within this export. All rows from the same entry share it. |
Document ID | The document the entry came from. |
Processed On | When the entry was processed (YYYY-MM-DD HH:MM:SS). |
File Name | The original file name. |
Your fields follow, in the order configured in the parser, using each field's display name as the column header.
Errors
| HTTP | Body | Cause |
|---|---|---|
400 | processed_from cannot be after processed_to. | The date range is reversed. |
400 | Invalid processed_from. Use YYYY-MM-DD format. | A date isn't in YYYY-MM-DD format. |
404 | {"detail": "Parser not found."} | No parser with this ID in your account. Check that you used the ID, not the slug. |
401 | {"detail": "..."} | See Authentication errors. |
Exports or webhooks?
Use exports when people or a scheduled job want a batch of data. Use webhooks when each result should flow into another system as soon as it's ready. See Schedule a monthly export for a ready-made job.