# Create or Update Batch ReinsContractCriteria

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

Endpoint: PUT /reinsurance-contracts/{reinsContractKey}/criterias-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Path parameters:

  - `reinsContractKey` (integer, required)
    ReinsContract Key

## Request fields (application/json):

  - `reinsContractCriteria_Key` (integer, required)
    Unique identifier for each criteria on this contract. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `criteria_Type` (string, required)
    Indicates if this is a Spec or Agg criteria.

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

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

  - `incurred_From` (string,null)
    The incurred (service date) from.

  - `incurred_Thru` (string,null)
    The incurred (service date) thru.

  - `paid_From` (string,null)
    The paid (check run date) from.

  - `paid_Thru` (string,null)
    The paid (check run date) thru.

  - `reinsContract_Key` (integer, required)
    References the ReinsContract.ReinsContract_Key on parent table. This holds the Spec or Agg Inccurred/Paid ranges that create the basis for claims being attached to transactions. Note: This field is marked as NOT NULL in the database and therefore required by the API.

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