# Billing Refund

Generate the necessary Billing adjustments for an Invoice refund and create a Distribution if needed.

Endpoint: POST /billing-refund
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)

  - `group_ID` (string)

  - `division_ID` (string)

  - `subscriber_ID` (string)

  - `premRate_Key` (integer)

  - `amount` (number)

  - `amount_Received` (number)

  - `volume` (number)

  - `payee_Level` (string)

  - `payor_ID` (string)

  - `account_Key` (integer)

  - `premPayment_Key` (integer)

  - `refund_Amount` (number)

  - `payment_ID` (string)

  - `payment_Name` (string)

  - `invoice_Level` (string)

  - `user_ID` (string)

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