> ## 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 voucher types > Get the voucher types of the tenant, sorted by their order ## OpenAPI ````yaml GET /v1/{tenantId}/voucher-types 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: 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. externalDocs: description: Find out more about Debbie here url: https://debbiecollect.com paths: /v1/{tenantId}/voucher-types: get: tags: - Voucher types summary: Get voucher types description: Get the voucher types of the tenant, sorted by their order operationId: get-voucher-types parameters: - in: path name: tenantId schema: type: string format: uuid required: true description: Id of the tenant the voucher types belong to - in: query name: page schema: type: integer example: 0 description: Page to get. Starting from 0. - in: query name: pageSize schema: type: integer example: 25 description: Number of items per page. 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/VoucherType' '401': $ref: '#/components/responses/UnauthorizedError' '422': $ref: '#/components/responses/UnprocessableContent' components: schemas: VoucherType: type: object properties: voucherTypeId: type: string format: uuid description: Id of the voucher type examples: - 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d label: type: string description: Display name of the voucher type examples: - Deposit category: type: string enum: - disbursement - fee - collectioncommission - payout - overpayment - vat - transaction - cost - courtcost - interest - principal description: Category of the voucher type examples: - transaction public: type: boolean description: >- Whether the voucher type is one of the built-in public types shared by every tenant, as opposed to a tenant-specific type examples: - true order: type: integer description: Sort order of the voucher type. The list is sorted by this value. examples: - 10 vat: type: boolean description: Whether vouchers of this type carry VAT examples: - false setting: type: - string - 'null' enum: - INTEREST_PERCENTAGE - INTEREST_FROM_TABLE - COMPOUND_INTEREST - FIXED_INTEREST - AMOUNT_FROM_TABLE - TEXT_AS_LABEL - null description: >- Behavior of vouchers of this type, e.g. how interest is calculated. Null when the type has no special behavior. examples: - null settingDetails: type: - object - 'null' description: >- Configuration of the behavior selected in setting. Its shape depends on the setting. Null when the type has no special behavior. editorSettings: type: - object - 'null' description: Settings for how vouchers of this type are edited in the Debbie apps 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}`. ````