> ## Documentation Index > Fetch the complete documentation index at: https://documentation.debbiecollect.com/llms.txt > Use this file to discover all available pages before exploring further. # Get billing vouchers > Get the fees and disbursements the creditor is charged on a billing. Only the fees that stand on their own are returned. A fee charged on a specific deposit is part of that deposit's distribution and is reported by [Get deposit distribution](/api-reference/endpoints/billing/get) as `collectionCommission` instead, so the two endpoints can be booked together without counting it twice. **Required scope:** `read:billings` ## OpenAPI ````yaml GET /v1/{tenantId}/billings/{billingId}/billing-vouchers openapi: 3.1.0 info: title: Debbie API Docs description: > The Debbie API is a RESTful interface, allowing you to programmatically update, add and access your data in the platform. It provides predictable URLs for accessing resources, and uses built-in HTTP features to receive commands and return responses. This makes it easy to communicate with third party systems. ## Idempotency The Debbie API supports idempotency for non-idempotent requests through the optional `Idempotency-Key` header. This ensures that retrying the same request multiple times will produce the same result, preventing duplicate operations. ### Using Idempotency Keys - Include an `Idempotency-Key` header with a unique string (we recommend UUIDs) - Maximum key length is 64 characters - Keys are valid for 48 hours - Responses served from the idempotency cache include an `Idempotency-Cached` header ### Example ```http Idempotency-Key: 123e4567-e89b-12d3-a456-426614174000 ``` ### Error Cases - Invalid key format: 400 Bad Request - Reusing a key for a different request: 400 Bad Request ### Best Practices - Use a new key for each unique business transaction - Use the same key when retrying a failed request - Store keys with request details for debugging contact: email: api-support@debbie.dk version: v0.1.0 servers: - url: https://api.debbiecollect.com security: - bearerAuth: [] tags: - name: Authorization description: Endpoints for interacting with authorization - name: Cases description: Endpoints for interacting with cases - name: Customers description: Endpoints for interacting with customers - name: Creditors description: Endpoints for interacting with creditors - name: Ultimate creditors description: >- Endpoints for interacting with ultimate creditors. An ultimate creditor is the original creditor behind the creditor on a case — for example when a debt collection agency forwards cases on behalf of its own client. On cases with an ultimate creditor, the creditor template mentions (name, address and company identifier) use the details of the ultimate creditor. - name: Updates description: Endpoints for interacting with updates - name: Users description: Endpoints for interacting with updates - name: Files description: Endpoints for interacting with files - name: Case vouchers description: Endpoints for interacting with case vouchers - name: Voucher types description: The voucher types of the tenant, used to categorize case vouchers - name: Interactions description: >- Interactions are messages and notes on a case, for example an incoming message from a debtor. - name: Billing description: Endpoints for interacting with billing - name: Transaction accounts description: >- Endpoints for interacting with transaction accounts — the bank and payment service provider accounts that payments are registered on - name: Links description: Endpoints for generating links - name: Webhooks description: >- Debbie provides a range of webhooks. To try them out please visit Debbie Caseworker and navigate to Settings --> Developers --> Webhooks. - name: End reasons description: Endpoints for interacting with end reasons - name: Case groups description: Endpoints for interacting with case groups externalDocs: description: Find out more about Debbie here url: https://debbiecollect.com paths: /v1/{tenantId}/billings/{billingId}/billing-vouchers: get: tags: - Billing summary: Get billing vouchers in a billing. description: >- Get the fees and disbursements the creditor is charged on a billing. Only the fees that stand on their own are returned. A fee charged on a specific deposit is part of that deposit's distribution and is reported by [Get deposit distribution](/api-reference/endpoints/billing/get) as `collectionCommission` instead, so the two endpoints can be booked together without counting it twice. **Required scope:** `read:billings` operationId: billing-vouchers parameters: - in: path name: tenantId schema: type: string format: uuid required: true description: Id of the tenant - in: path name: billingId schema: type: string format: uuid required: true description: Id of the billing - in: query name: page schema: type: integer minimum: 0 default: 0 required: false description: Zero-based page number - in: query name: pageSize schema: type: integer minimum: 1 maximum: 1000 default: 25 required: false description: Number of vouchers per page - in: query name: category schema: type: string example: '["fee","disbursement"]' required: false description: >- JSON encoded list of the categories to return, `fee` and/or `disbursement`. Omit to get both. responses: '200': description: Successful operation content: application/json: schema: type: object properties: meta: type: object properties: currentPage: type: integer example: 0 pageSize: type: integer example: 25 items: type: array items: $ref: '#/components/schemas/BillingVoucher' '401': $ref: '#/components/responses/UnauthorizedError' '422': $ref: '#/components/responses/UnprocessableContent' components: schemas: BillingVoucher: type: object properties: billingVoucherId: type: string format: uuid description: Id of the billing voucher id: type: integer description: Sequential id of the billing voucher category: type: string enum: - fee - disbursement description: >- Whether the entry is a fee charged by the collector or a disbursement laid out on the creditor's behalf voucherTypeId: type: string format: uuid description: Id of the voucher type label: type: string description: Display name of the voucher type amount: type: integer description: >- Amount in base currency, excluding VAT. For example 1.00 will be sent as 100. currency: $ref: '#/components/schemas/Currency' referenceId: type: - string - 'null' description: Reference id of the entry text: type: - string - 'null' description: Text on the entry vat: type: array description: The VAT charged on this entry. Empty when the entry carries no VAT. items: type: object properties: billingVoucherId: type: string format: uuid description: Id of the VAT billing voucher voucherTypeId: type: string format: uuid description: Id of the voucher type label: type: string description: Display name of the voucher type amount: type: integer description: Amount in base currency. For example 1.00 will be sent as 100. caseId: type: string format: uuid description: Id of the case the entry belongs to caseSequentialId: type: - integer - 'null' description: Sequential id of the case the entry belongs to creditorId: type: - string - 'null' format: uuid description: Id of the creditor being charged creditorName: type: - string - 'null' description: Name of the creditor being charged creditorReferenceId: type: - string - 'null' description: Your own id for the creditor billingId: type: - string - 'null' format: uuid description: Id of the billing the entry is settled on billingAppendixId: type: - string - 'null' format: uuid description: Id of the settlement appendix the entry belongs to createdAt: type: string description: Created at timestamp of the entry createdBy: type: - object - 'null' description: Actor that created the entry properties: id: type: string format: uuid description: Id of the actor type: type: string description: Type of the actor caseVoucher: type: - object - 'null' description: The case voucher the entry relates to, when it relates to one depositCaseVoucher: type: - object - 'null' description: The deposit the entry relates to, when it relates to one Currency: type: string enum: - DKK - SEK - NOK - USD - EUR - GBP - CHF description: Currency responses: UnauthorizedError: description: Access token missing or invalid UnprocessableContent: description: Unable to process the contained instructions. securitySchemes: bearerAuth: type: http scheme: bearer description: >- Authentication can be done by using a bearer token in the Authorization header. This is done using the following format `Authorization: Bearer {token}`. ````