> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanova.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Export lead entries

> GET /lead/{lead_id}/entry/export/

Downloads a lead list's entries as a CSV or Excel file.

<Note>
  Requires a Management API key with `MANAGEMENT_API` (or `MANAGEMENT_API_SANDBOX`) quota, and the `LEAD_GENERATION_ENTRY_CAN_VIEW` permission, sent as the raw `Authorization` header value — see the [Management API overview](/api-reference/management-api/overview).
</Note>

<ParamField path="lead_id" type="string" required>
  The lead list's `lead_id`.
</ParamField>

<ParamField query="file_format" type="string" default="csv">
  `csv`, `xls`, or `xlsx`.
</ParamField>

<ParamField query="from" type="string">
  Only entries created on or after this date (`YYYY-MM-DD`).
</ParamField>

<ParamField query="to" type="string">
  Only entries created on or before this date (`YYYY-MM-DD`).
</ParamField>

<ParamField query="ids" type="string">
  Comma-separated entry UUIDs to scope the export to a specific selection — mirrors the dashboard's "download selected" action. Invalid UUIDs are silently ignored rather than rejected.
</ParamField>

<ParamField query="search" type="string">
  Same substring search as [List lead entries](/api-reference/management-api/leads/entry-list) — mirrors "download filtered results".
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request GET \
    --url 'https://api.scanova.io/lead/L9c2f4a1e/entry/export/?file_format=csv&from=2026-08-01&to=2026-08-31' \
    --header 'Authorization: YOUR_API_KEY' \
    --output entries.csv
  ```
</RequestExample>

The response is a file download (`Content-Type: text/csv`, or the XLSX MIME type for `xls`/`xlsx`), not JSON, with `Content-Disposition: attachment; filename=<LeadListName>-<timestamp>.<ext>`.

<Note>
  The exported file always includes a `tracking_id` column, regardless of tracking permissions elsewhere on the account. If a submitting QR Code has since been deleted, its column value renders as `<qrid> (Deleted)` rather than failing the export. With zero matching entries, the file still contains a header row (derived from the lead form's own question labels) rather than being empty.
</Note>

<Warning>
  On a free-plan account (`plan_type` 1), the export is capped at 25 rows — if more entries matched, two trailing rows are appended noting the cap and prompting an upgrade.
</Warning>

`400` with a plain-text body (not the standard DRF error shape) if `file_format` isn't one of `csv`, `xls`, `xlsx`:

```json 400 theme={null}
{ "detail": "requested file format unknown" }
```

## Related

* [List lead entries](/api-reference/management-api/leads/entry-list) — the JSON equivalent, with the same filters.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota architecture this endpoint is part of.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /lead/{lead_id}/entry/export/
openapi: 3.1.0
info:
  title: Scanova Management API (v2)
  description: >-
    The complete Scanova Management API — every endpoint available at
    api.scanova.io (QR codes, folders, tags, leads, forms, analytics, plans,
    shared users & roles), plus the token-creation and usage-stats endpoints
    used to authenticate against it. Every path and request/response shape below
    was verified live against a real API key and the actual running backend
    (Phase 7, 2026-08-16) — not guessed from reading urls.py alone.
  version: 2.0.0
servers:
  - url: https://api.scanova.io
    description: Management API — QR/folder/tag/lead/form/analytics/plans endpoints
security:
  - apiKeyAuth: []
paths:
  /lead/{lead_id}/entry/export/:
    get:
      summary: Export lead entries
      operationId: exportManagedLeadEntries
      responses:
        '200':
          description: CSV or XLSX file download.
components:
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Send your Management API key as the raw value of the Authorization
        header — no "Bearer " or "Token " prefix, and no other characters.
        Example: `Authorization: 401f7ac837da42b97f613d789819ff93537bee6a`. A
        header containing more than one space-separated part is rejected
        outright. Requests also require the request's Host header to be the
        management API host (e.g. api.scanova.io) — the same key sent to the
        regular API host will not authenticate.

````