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

# List purchasable quota top-up packs

> GET /plans/quota-topup-packs/

Lists the top-up packs currently available for purchase on the **Management API** host (`api.scanova.io`), authenticated with your raw Management API key.

```
GET https://api.scanova.io/plans/quota-topup-packs/
Authorization: 401f7ac837da42b97f613d789819ff93537bee6a
```

<RequestExample>
  ```bash cURL theme={null}
  curl "https://api.scanova.io/plans/quota-topup-packs/" \
    -H "Authorization: 401f7ac837da42b97f613d789819ff93537bee6a"
  ```
</RequestExample>

<ResponseExample>
  ```json 200 theme={null}
  [
    { "codename": "AI_QR_TOKENS_500", "name": "500 AI QR credits", "quota_codename": "AI_QR_TOKENS", "quota_name": "AI QR Tokens", "amount": 500, "price_usd": "9.00", "price_inr": "749.00", "expiry_days": 90 }
  ]
  ```
</ResponseExample>

Not paginated — a small, mostly-static catalog.

<Warning>
  This is a read-only catalog. There's no Management API endpoint to actually purchase a pack — that happens through the account's regular payment/checkout flow (the dashboard, or the payments endpoints), not here.
</Warning>

## Related

* [List your purchased quota top-ups](/api-reference/management-api/plans/quota-topups) — what the account has actually bought from this catalog.
* [Current plan](/api-reference/management-api/plans/current) — the account's base plan quotas, which top-ups add to.
* [Management API overview](/api-reference/management-api/overview) — the auth scheme and quota rules that apply to this endpoint.


## OpenAPI

````yaml api-reference/openapi/management-api.json GET /plans/quota-topup-packs/
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:
  /plans/quota-topup-packs/:
    get:
      summary: List purchasable quota top-up packs
      description: >-
        Lists the top-up packs currently available for purchase (e.g. extra
        AI-QR generation credits). This is a read-only catalog — purchasing a
        pack happens through the regular payment/checkout flow, not through the
        Management API.
      operationId: listManagedQuotaTopUpPacks
      responses:
        '200':
          description: Available top-up packs. Not paginated.
          content:
            application/json:
              example:
                - codename: AI_QR_TOKENS_500
                  name: 500 AI QR credits
                  quota_codename: AI_QR_TOKENS
                  quota_name: AI QR Tokens
                  amount: 500
                  price_usd: '9.00'
                  price_inr: '749.00'
                  expiry_days: 90
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.

````