# Create or Update Batch ClaimRepriceRemove Create or Update multiple ClaimRepriceRemove at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /claim-reprice-remove-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Request fields (application/json): - `claimRepriceRemove_Key` (integer, required) Unique identifer for each claim reprice remove entry. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `apply_Network_ID` (string,null) Notes the new Network that should be applied to this claim if the Reprice Remove values match the inbound claim information. - `division_ID` (string,null) The patients (or Subscribers) enrollment information, references Subenrollment.Division_ID. - `effective_Date` (string,null) Date when the reprice remove code becomes/became effective. - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `ex_Code` (string,null) The ExCode applied to this claim reprice entry. - `group_ID` (string,null) The patients (or Subscribers) enrollment information, references Subenrollment.Group_ID. - `remove_Repriced_Network_ID` (boolean, required) Notes if the Repriced_Network_ID value should be cleared as part of the Reprice Remove adjudication process. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `repriced_Network_ID` (string,null) The Repriced Network ID referenced on this claim to determine if rules apply. - `tax_ID` (string,null) The Provider Tax ID referenced on this claim to determine if rules apply. - `term_Date` (string,null) Date when the reprice remove code no longer applies. - `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 - `provider_Has_Network_ID` (string,null) Indicates that this configuration requires the provider be in the Repriced Network before this applies. ## 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