> ## 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 analytics

> POST /lead/analytics/export/

Downloads lead analytics (all three breakdowns: entry counts, conversion, and source) as a file.

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

<ParamField body="q" type="array" required>
  Same as [Get lead analytics](/api-reference/management-api/leads/analytics) — `lead_id`s or QR `url_hash`es, per `filter_by`.
</ParamField>

<ParamField body="filter_by" type="string" default="lead_id">
  `lead_id` (default) or `qr_hash`.
</ParamField>

<ParamField query="file_format" type="string" default="csv">
  `csv` (a ZIP of one CSV per breakdown), or `xls`/`xlsx` (one workbook with three sheets).
</ParamField>

<ParamField query="from" type="string">
  Start date (`YYYY-MM-DD`). Defaults to 7 days before `to`.
</ParamField>

<ParamField query="to" type="string">
  End date (`YYYY-MM-DD`). Defaults to today.
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl --request POST \
    --url 'https://api.scanova.io/lead/analytics/export/?file_format=xlsx&from=2026-08-01&to=2026-08-31' \
    --header 'Authorization: YOUR_API_KEY' \
    --header 'Content-Type: application/json' \
    --data '{ "q": ["L9c2f4a1e"] }' \
    --output lead_analytics.xlsx
  ```
</RequestExample>

The response is a file download — `application/zip` with `Content-Disposition: attachment; filename=lead_analytics.zip` for `csv`, or the XLSX MIME type with `filename=lead_analytics.xlsx` for `xls`/`xlsx`. Unlike [Get lead analytics](/api-reference/management-api/leads/analytics), there's no `type` filter — the export always includes all three breakdowns.

`400` with a plain-text body if `file_format` isn't recognized:

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

## Related

* [Get lead analytics](/api-reference/management-api/leads/analytics) — the JSON equivalent, with a `type` filter.
* [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 POST /lead/analytics/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/analytics/export/:
    post:
      summary: Export lead analytics
      operationId: exportManagedLeadAnalytics
      responses:
        '200':
          description: ZIP of CSVs or a multi-sheet 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.

````