> ## 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.

# Bulk Apply Transaction Payment to Selected Invoices

> Apply a single transaction payment to multiple selected invoices.

Supports two selection modes:
- Explicit invoice IDs (``invoice_ids``)
- Filter-based selection (``filters``) for "select all matching" behaviour

Reuses :meth:`MarkInvoicePaidView.apply_transaction_payment` so that
line-level payment splitting, FX gain/loss realisation, and transaction
cleanup are all respected.  A single ``DraftQueue`` is created when
approval is required.



## OpenAPI

````yaml https://api.meetcampfire.com/api/schema?format=json post /coa/api/v1/invoice/bulk-apply-payment
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/invoice/bulk-apply-payment:
    post:
      tags:
        - Accounts Receivable
      summary: Bulk Apply Transaction Payment to Selected Invoices
      description: >-
        Apply a single transaction payment to multiple selected invoices.


        Supports two selection modes:

        - Explicit invoice IDs (``invoice_ids``)

        - Filter-based selection (``filters``) for "select all matching"
        behaviour


        Reuses :meth:`MarkInvoicePaidView.apply_transaction_payment` so that

        line-level payment splitting, FX gain/loss realisation, and transaction

        cleanup are all respected.  A single ``DraftQueue`` is created when

        approval is required.
      operationId: coa_api_v1_invoice_bulk_apply_payment_create
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/BulkApplyInvoicePayment'
          application/x-www-form-urlencoded:
            schema:
              $ref: '#/components/schemas/BulkApplyInvoicePayment'
          multipart/form-data:
            schema:
              $ref: '#/components/schemas/BulkApplyInvoicePayment'
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                type: object
                additionalProperties: {}
          description: ''
      security:
        - knoxApiToken: []
components:
  schemas:
    BulkApplyInvoicePayment:
      type: object
      properties:
        transaction_id:
          type: integer
        invoice_ids:
          type: array
          items:
            type: integer
          nullable: true
        filters:
          allOf:
            - $ref: '#/components/schemas/BulkApplyInvoicePaymentFilters'
          nullable: true
      required:
        - transaction_id
    BulkApplyInvoicePaymentFilters:
      type: object
      properties:
        entity:
          type: integer
          nullable: true
        client:
          type: integer
          nullable: true
        status:
          type: string
          nullable: true
        max_date:
          type: string
          format: date
          nullable: true
        search_query:
          type: string
          nullable: true
  securitySchemes:
    knoxApiToken:
      type: apiKey
      in: header
      name: Authorization
      description: Token-based authentication with required prefix "Token"

````