# Create or Update Batch ReinsContractTrans Create or Update multiple ReinsContractTrans 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}/transactions-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): - `reinsContractTrans_Key` (integer, required) Unique identifier for each transaction being generated on this contract. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `description` (string,null) The description of this transaction. - `entry_Date` (string) User that first added the record to the system - `entry_User` (string,null) Date record was first added to the system - `member_Seq` (string,null) The member on this transaction. - `reinsContract_Key` (integer, required) References the ReinsContract.ReinsContract_Key on parent record. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `submitted_Date` (string,null) The date the reinsurance claims (transaction) was submitted to the reinsurance carrier. - `subscriber_ID` (string,null) The member on this transaction. - `transaction_Amount` (number,null) The total amount of the claims attached to this transaction. - `transaction_Claim_Number` (string,null) The transaction ID associated with this reinsurance claim. - `transaction_Date` (string,null) The date the transaction was generated. - `transaction_Status` (string,null) The status of this transaction as it is in the process of being reimbursed. - `transaction_Type` (string,null) The type of transaction being created. This is a spec transaction or agg transaction. - `update_Date` (string) User that last updated the record in the system - `update_User` (string,null) Date the record was last updated in the system - `attachment_Point` (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