curl --request GET \
--url 'https://api.scanova.io/payment/205/receipt/download/' \
--header 'Authorization: YOUR_API_KEY' \
--output receipt.pdf
Payments
Download a receipt
GET /payment//receipt/download/
GET
/
payment
/
{payment_id}
/
receipt
/
download
/
curl --request GET \
--url 'https://api.scanova.io/payment/205/receipt/download/' \
--header 'Authorization: YOUR_API_KEY' \
--output receipt.pdf
Downloads the locally-generated receipt for one payment — always this document, never the real GST-compliant invoice, regardless of whether one is available.
Use Download an invoice/receipt instead if you want the real invoice when one exists, with this same receipt as its fallback.
Requires the
BillingInvoiceCanDownload permission.integer
required
Payment ID, from List payment history.
curl --request GET \
--url 'https://api.scanova.io/payment/205/receipt/download/' \
--header 'Authorization: YOUR_API_KEY' \
--output receipt.pdf
The response is a binary file (PDF), not JSON.
404 if payment_id isn’t owned by this account.
Related
- Download an invoice/receipt — prefers the real invoice, falls back to this same receipt.
- List payment history
- Management API overview — the auth scheme and quota architecture this endpoint is part of.
Authorizations
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.
Path Parameters
Response
The receipt, as a binary PDF attachment.
Was this page helpful?