> ## Documentation Index > Fetch the complete documentation index at: https://docs.campfire.ai/llms.txt > Use this file to discover all available pages before exploring further. # List Accounting Bills > Retrieve a paginated list of accounting bills with comprehensive filtering, search, and sorting capabilities. This endpoint provides complete access to your bills data with: - Advanced filtering by date ranges, payment status, vendors, entities, and currency - Full-text search across bill numbers, vendor names, addresses, and bill messages - Flexible sorting by any field including calculated fields (totals, amounts due, etc.) - Comprehensive pagination with customizable page sizes - Aging calculations and payment status categorization - Automatic calculation of totals, amounts paid, and amounts due **Deleted Records Support:** - When include_deleted=true: Returns ONLY deleted bills with minimal data (id, is_deleted, deleted_at, last_modified_at) - When include_deleted=false or omitted: Returns ONLY active bills with full data - Timestamp filtering (last_modified_at__gte/lte) works with both active and deleted records ## OpenAPI ````yaml https://api.meetcampfire.com/api/schema?format=json get /coa/api/v1/bill/ openapi: 3.0.3 info: title: Campfire Developer APIs version: 1.0.0 description: > ## Introduction Campfire's developer APIs offer granular access to Campfire's core accounting, revenue recognition, and financial data features. These APIs are designed to be used by developers to build custom integrations, automate workflows, and perform any other programmatic operations. servers: - url: https://api.meetcampfire.com description: Production server security: [] tags: - name: Cash Management description: Operations related to accounts, transactions, and other bank-related data. - name: Core Accounting description: >- Operations related to core accounting data, such as the chart of accounts, entity management, and the general ledger. - name: Revenue Recognition description: >- Operations related to revenue recognition, contract management, and contract data aggregation. - name: Accounts Receivable description: Operations related to invoicing and the AR subledger - name: Accounts Payable description: Operations related to billing and the AP subledger. - name: Financial Statements description: Operations related to financial statement generation and data aggregation. - name: Settings description: Operations related to system and accounting settings configuration. paths: /coa/api/v1/bill/: get: tags: - Accounts Payable summary: List Accounting Bills description: |2- Retrieve a paginated list of accounting bills with comprehensive filtering, search, and sorting capabilities. This endpoint provides complete access to your bills data with: - Advanced filtering by date ranges, payment status, vendors, entities, and currency - Full-text search across bill numbers, vendor names, addresses, and bill messages - Flexible sorting by any field including calculated fields (totals, amounts due, etc.) - Comprehensive pagination with customizable page sizes - Aging calculations and payment status categorization - Automatic calculation of totals, amounts paid, and amounts due **Deleted Records Support:** - When include_deleted=true: Returns ONLY deleted bills with minimal data (id, is_deleted, deleted_at, last_modified_at) - When include_deleted=false or omitted: Returns ONLY active bills with full data - Timestamp filtering (last_modified_at__gte/lte) works with both active and deleted records operationId: coa_api_v1_bill_retrieve parameters: - in: query name: currency schema: type: string description: Filter by currency code (e.g., USD, EUR) - in: query name: download schema: type: boolean default: false description: If true, triggers async download workflow and sends bills via email - in: query name: end_date schema: type: string description: Filter bills with bill_date on or before this date (YYYY-MM-DD) - in: query name: entity schema: type: integer description: >- Filter by entity ID. Can be specified multiple times for multiple entities explode: true style: form - in: query name: include_deleted schema: type: boolean default: false description: >- When set to 'true', returns ONLY deleted records instead of active records. Deleted records contain minimal data: 'id', 'is_deleted=true', 'deleted_at' timestamp, and 'last_modified_at'. When 'false' or omitted, returns ONLY active records. This provides clean separation between active and deleted data. - in: query name: last_modified_at__gte schema: type: string description: >- Filter for records modified on or after this timestamp. Format: ISO 8601 (e.g., '2024-01-01T00:00:00Z' or '2024-01-01'). Works with both active records and deleted records (filters by deletion time for deleted records). - in: query name: last_modified_at__lte schema: type: string description: >- Filter for records modified on or before this timestamp. Format: ISO 8601 (e.g., '2024-12-31T23:59:59Z' or '2024-12-31'). Works with both active records and deleted records (filters by deletion time for deleted records). - in: query name: limit schema: type: integer default: 50 description: 'Number of results to return per page (default: 50, max: 1000)' - in: query name: offset schema: type: integer default: 0 description: The initial index from which to return the results - in: query name: q schema: type: string description: >- Search query - searches by mailing address, bill number, message on bill, or vendor name - in: query name: sort schema: type: string default: '-bill_date' description: >- Sort order. Use field name for ascending, -field for descending. Special fields: vendor_name, total_amount, amount_paid, amount_due, payment. Default: -bill_date - in: query name: start_date schema: type: string description: Filter bills with bill_date on or after this date (YYYY-MM-DD) - in: query name: status schema: type: string enum: - '1_30' - '31_60' - '61_90' - '91_120' - current - open - over_120 - paid - partially_paid - past_due - payment_not_found - payment_pending - unpaid - voided description: Filter by payment status - in: query name: vendor schema: type: integer description: >- Filter by vendor ID. Can be specified multiple times for multiple vendors explode: true style: form responses: '200': description: No response body security: - knoxApiToken: [] components: securitySchemes: knoxApiToken: type: apiKey in: header name: Authorization description: Token-based authentication with required prefix "Token" ````