# Create or Update Batch ChecksDetail

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

Endpoint: PUT /checks/{checkID}/details-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Path parameters:

  - `checkID` (integer, required)
    Check ID

## Request fields (application/json):

  - `check_ID` (integer, required)
    ID of the check. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `item_Seq` (integer, required)
    Sequential identifier of the check item. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `adjustment` (number,null)
    Adjustment amount for the check line.

  - `admin_Amt` (number,null)
    Admin fee associated with the check line.

  - `amount_Due` (number,null)
    Total amount due for the check.

  - `claim_Number` (integer,null)
    Number of the claim associated with the check line.

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

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

  - `interest` (number,null)
    Interest amount associated with the check line.

  - `item_Date` (string,null)
    Date when the check line item was received.

  - `item_Description` (string,null)
    Description of the item associated with the check line.

  - `item_Type` (string,null)
    Identifies the type of item associated with the check line.

  - `message` (string,null)
    The message on the check.

  - `processed` (string,null)
    Indicates tha the check has been processed.

  - `provider_ID` (string,null)
    ID of the Provider associated with the check line.

  - `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

  - `offset_Amt` (number,null)

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