# Create or Update Batch Funding

Create or Update multiple Funding at once.  If the entity exists, it will be updated.  If the entity does not exist, it will be created.

Endpoint: PUT /funding-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Request fields (application/json):

  - `funding_Key` (integer, required)
    ID of the Funding record.  Note: The database will apply a default value of 0 for this field if a value is not provided.  This field is also marked as NOT NULL in the database and therefore required by the API.  If you do not have a value for this field, supply the database default value of 0 to meet the API requirements and ensure that the functionality occurs as expected.

  - `account_Key` (integer,null)
    ID of the funding account.

  - `cleared_Amount` (number,null)
    Amount that was Cleared.

  - `cleared_Date` (string,null)
    Date the Amount was Cleared.

  - `deposit_Key` (integer,null)
    ID of the Deposit.

  - `entry_Date` (string)
    Date record was first added to the system

  - `entry_User` (string,null)
    User that first added the record to the system

  - `funding_Status` (string,null)
    Status of the Funding.

  - `funding_Type` (string,null)
    Type of the Funding.

  - `issue_Amount` (number,null)
    Amount Issued of the Funding record.

  - `issue_Date` (string,null)
    Date of the Issue.

  - `issue_ID` (string,null)
    ID of the Issue.

  - `issue_Name` (string,null)
    Name of the Issue.

  - `issue_Type` (string,null)
    The transaction type of the Issue Amount.

  - `payor_ID` (string,null)
    ID of the Payor associated with the Funding record.

  - `received_Date` (string,null)
    Date Funding was Received.

  - `update_Date` (string)
    Date the record was last updated in the system

  - `update_User` (string,null)
    User that last updated the record in the system

## Response 207 fields (text/plain):

  - `data` (array,null)

  - `data.id` (array, required)
    List of key/value pairs that represent the unique id for the entity operation.

  - `data.id.key` (string,null)

  - `data.id.value` (any,null)

  - `data.status` (integer, required)
    http status of the operation (eg, 200, 201, 500)

  - `data.body` (string, required)
    operation message (eg, Updated, Created, Error message)

  - `error` (object)

  - `error.detail` (string,null)
    A human-readable explanation specific to this occurrence of the problem.

  - `error.instance` (string,null)
    A URI reference that identifies the specific occurrence of the problem.It may
or may not yield further information if dereferenced.

  - `error.status` (integer)
    The HTTP status code([RFC7231], Section 6) generated by the origin server for
this occurrence of the problem.

  - `error.title` (string,null)
    A short, human-readable summary of the problem type.It SHOULD NOT change from
occurrence to occurrence of the problem, except for purposes of localization(e.g.,
using proactive content negotiation; see[RFC7231], Section 3.4).

  - `error.type` (string,null)
    A URI reference [RFC3986] that identifies the problem type. This specification
encourages that, when dereferenced, it provide human-readable documentation for
the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member
is not present, its value is assumed to be "about:blank".

  - `debug` (object)

  - `debug.activityID` (string, required)


## Response 401 fields