# Billing Auto-Apply

Auto Apply Payment based on specified configuration options.

Endpoint: POST /billing-auto-apply
Version: v1
Security: apiKeyAuth, bearerAuth

## Security:

  - `apiKeyAuth` (unknown)
    apiKey in header x-api-key

  - `bearerAuth` (unknown)
    http bearer JWT

## Header parameters:

  - `vbasoftware-database` (string, required)
    Target database

## Request fields (application/json):

  - `invoice_Key` (integer)

  - `premPayment_Key` (integer)

  - `payment_Posted` (number)

  - `payment_Posted_Date` (string)

  - `payment_ID` (string)

  - `received_Date` (string)

  - `autoApplyOption` (integer)

  - `autoApplyAdjustmentOption` (integer)

  - `autoApplyCategories` (array)

  - `autoApplySubscribers` (array)

## Response 202:

  - `202` (unknown)
    Accepted for processing

## Response 401:

  - `401` (unknown)
    Unauthorized

## Response 403:

  - `403` (unknown)
    Forbidden. The x-api-key header is missing or not valid. The API gateway sends this response, not VBAPI, so the body is not the VBAPI envelope; see Errors and troubleshooting.

## Response 429:

  - `429` (unknown)
    Too many requests. The limit is 25 requests per second sustained, with bursts up to 50, per API key. Wait and retry with exponential backoff and jitter.