> ## Documentation Index > Fetch the complete documentation index at: https://docs.venlyfinance.com/llms.txt > Use this file to discover all available pages before exploring further. # Download an invoice PDF > Download the PDF of an issued invoice. **Requires scope:** `view:billing` — see [Required scopes](/getting-started/authentication#required-scopes-finance-api). Returns the invoice as **raw PDF bytes** — not wrapped in the JSON envelope. Errors still use the JSON `ErrorResponse`. The `Content-Disposition` header carries a filename derived from the invoice number. A `404` always means the invoice is not yours to read; an invoice you *can* read whose PDF cannot be produced is `500 billing-provider-error`, so a rendering fault is never mistaken for a wrong id. ## OpenAPI ````yaml api-reference/Finance-API-Specs.yaml GET /billing/invoices/{invoiceId}/download openapi: 3.1.0 info: title: Venly Finance API description: > REST API for the Venly Finance platform: - Party management (Individuals & Organisations) - Identity verification — hosted KYC/KYB links and Sumsub share-token forwarding - Account management with party association - Wallet balances & token allowances on supported chains - Virtual bank accounts for global pay-in (EUR SEPA, USD ACH/WIRE/RTP/SWIFT) - Fiat-to-crypto payment sessions (pay-in) - Bank pay-outs — beneficiary allow-listing, routes, and PULL/PUSH pay-outs - Account-to-account fiat & crypto transfers - EIP-2612 permits and allowances - Webhook registration for asynchronous event delivery ## Authentication All endpoints use OAuth2 client credentials. Obtain a token first, then include it in every request: **Step 1 — Get a token:** ```bash curl -X POST https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=client_credentials&client_id={CLIENT_ID}&client_secret={CLIENT_SECRET}" ``` **Step 2 — Use the token:** ``` Authorization: Bearer {access_token} ``` Tokens expire after **5 minutes**. Implement refresh logic in your client. ## Selecting a tenant A token that grants more than one tenant must say which one each request is for, in the `x-tenant-id` header. With a single-tenant token, omit it. Any value you send must exactly match a tenant the token grants; a missing, malformed or foreign value is answered with a generic `403 forbidden` that reveals nothing about which tenants exist. Send the header at most once. ## Request correlation Every response — including `401` and `403` — carries an `X-Correlation-Id` header identifying the operation in our logs. Quote it in a support request. You may supply your own, as `X-Correlation-Id` or (as a fallback) `X-Request-Id`, matching `^[A-Za-z0-9_.:-]{1,64}$`. A value outside that shape is replaced with a generated one rather than rejected. version: 1.10.0 contact: name: Venly Support email: support@venly.io url: https://docs.venlyfinance.com license: name: Proprietary x-logo: url: https://venlyfinance.com/logo.png x-security-contact: security@venly.io servers: - url: https://api.venlyfinance.com/v1 description: Production - url: https://api-staging.venlyfinance.com/v1 description: Staging security: - OAuth2: [] tags: - name: Parties description: Party management (Individuals & Organisations) - name: Accounts description: Account management, party-role associations - name: Wallets description: Blockchain wallet balances - name: Virtual Bank Accounts description: Virtual bank account payment references for global payments - name: Fiat-to-crypto Payment Sessions description: >- Hosted fiat-to-crypto pay-in sessions. **Coming soon** — not yet enabled; use a virtual bank account to receive fiat today. - name: Payout Bank Accounts description: Allow-listing beneficiary bank accounts as pay-out destinations - name: Payout Routes description: >- Account-scoped routes pairing a beneficiary bank account with a crypto deposit asset - name: Payouts description: Crypto-to-fiat pay-outs over a registered route - name: Transfers description: Fiat and crypto transfer operations between accounts - name: Permits description: EIP-712 permit signature management for token approvals - name: Supported Assets description: >- Discover which chains and assets your tenant can settle in, and whether an account can use them yet. - name: Allowances description: Token allowance management for wallets - name: Webhooks description: Webhook registration, delivery testing and delivery history - name: Pay-Ins description: >- The pay-in ledger — every fiat credit that settled (or failed to settle) into an account wallet - name: Billing description: The invoices Venly has issued to your company - name: API Credentials description: Self-service management of your company's OAuth client credentials - name: Company description: Your own company profile paths: /billing/invoices/{invoiceId}/download: parameters: - $ref: '#/components/parameters/TenantId' get: tags: - Billing summary: Download an invoice PDF description: > **Requires scope:** `view:billing` Downloads the PDF of an issued invoice billed to your company. Ownership and issuance status are checked before the document is fetched; unknown, foreign, unsent and voided invoices all answer the same `404`. Success is **raw PDF bytes** without the JSON response envelope; errors use the usual JSON `ErrorResponse`. A `404` always means the invoice itself is not yours to read. An invoice that *is* readable but whose PDF cannot be produced is a `500 billing-provider-error`, never a `404`, so a rendering fault is never mistaken for a wrong id. operationId: downloadInvoice parameters: - $ref: '#/components/parameters/InvoiceId' responses: '200': description: Invoice PDF attachment headers: Content-Disposition: description: >- Attachment filename derived from the invoice number, falling back to the invoice id schema: type: string example: attachment; filename="invoice-INV-042.pdf" Content-Length: description: PDF size in bytes schema: type: integer format: int64 content: application/pdf: schema: type: string format: binary '400': description: Malformed `invoiceId` (not a UUID) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': $ref: '#/components/responses/Unauthorized' '403': description: Forbidden — the token lacks `view:billing`. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: '`invoice-not-found` — unknown, foreign, unsent or voided invoice' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '422': description: >- `billing-not-configured` — your company is not linked to a billing customer yet. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: >- `billing-provider-error` — the billing system rejected the request, or holds the invoice but could not produce its PDF. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '503': description: >- `billing-provider-unavailable` — the billing system could not be reached. Retry. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: parameters: TenantId: name: x-tenant-id in: header required: false description: > Which tenant the request is scoped to, among those your token grants. Omit it when the token grants exactly one tenant; it is **required** when the token grants more than one. A supplied value must exactly match a tenant the token grants. Absent when required, blank, malformed, or naming a tenant the token does not grant — each gets the same generic `403 forbidden`, which reveals neither whether a tenant exists nor which ones you may use. Send the header once: a repeated header is rejected the same way. schema: type: string format: uuid example: 3fa85f64-5717-4562-b3fc-2c963f66afa6 InvoiceId: name: invoiceId in: path required: true description: Invoice identifier, as returned by the invoice list schema: type: string format: uuid example: 7f68c0d4-4d55-4bd8-9b0e-1cfb0255c554 schemas: ErrorResponse: type: object description: Error response wrapper properties: success: type: boolean description: Always false for error responses example: false errors: type: array description: List of errors that occurred items: $ref: '#/components/schemas/ErrorBody' result: type: object nullable: true description: Null or omitted when success is false ErrorBody: type: object description: Individual error details properties: code: type: string description: Machine-readable error code example: invalid-request message: type: string description: Human-readable error message example: The request contains invalid parameters. responses: Unauthorized: description: Authentication required or failed (401) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: success: false errors: - code: unauthenticated message: Please authenticate to perform this action. securitySchemes: OAuth2: type: oauth2 description: > OAuth2 client credentials flow. Token endpoints: - Staging: https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token - Production: https://login.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token flows: clientCredentials: tokenUrl: >- https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token scopes: {} ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.