Exports

Exports get accepted responses out of Fillo — as a CSV file from the dashboard, or as JSON your server reads through the Management API.

Export CSV from the dashboard

Open a form and choose Responses.

1. Set the date, search, source, respondent, and field filters you need.
2. Check the visible result count and clear any accidental condition.
3. Choose CSV.

The export streams every matching response, not only the rows loaded in the browser. Columns come from the current schema plus up to 200 recent stored versions, so a field that exists only in an older version can stay in raw storage while falling outside that working column set.

CSV includes respondent name, email, and ID columns when the accepted result set contains identified responses. File answers are formatted as references, not embedded file bytes.

Read JSON from your server

Create a workspace API key with responses:read, keep it in a server secret store, and page through the Management API:

curl -G "https://fillo.so/api/v1/manage/forms/FORM_ID/responses" \
  -H "Authorization: Bearer $FILLO_KEY" \
  --data-urlencode "range=30d" \
  --data-urlencode "limit=100"

The response is { data, nextCursor }. Pass nextCursor back as cursor until it's null. The API returns structured answer JSON, form version IDs, source metadata, and file references under the scopes described in Management API.

Time and spreadsheet behavior

The dashboard currently renders operator timestamps in the Europe/London display zone. CSV writes the Received column as an ISO 8601 UTC instant, such as 2026-07-14T10:05:00.000Z. Convert it explicitly in your spreadsheet or warehouse — don't treat it as local wall time.

CSV cells that begin with spreadsheet formula characters are prefixed to prevent formula execution, then quoted. That changes how a spreadsheet interprets the cell, not the stored response.

Current format limits

Fillo currently provides dashboard CSV and Management API JSON. There's no PDF response document and no downloadable JSON file in the dashboard. When a document is part of your workflow, build the PDF in your own backend from the scoped API or a signed webhook.

Held submissions are excluded from normal exports until an owner releases them. And deleting a Fillo response doesn't remove an export already saved elsewhere.

Plan status

CSV export and the Management API are available on every plan. API keys remain subject to their scopes and rate limits.

Related

• Responses and insights: Filter the response set before exporting.
• Management API: Read structured responses with a scoped server key.
• Data retention and deletion: Delete the Fillo copy and plan for downstream copies.