# Create or Update Batch Grievance Create or Update multiple Grievance at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /grievances-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Request fields (application/json): - `grievance_Key` (integer, required) ID number of the grievance. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `admin_Change` (string,null) Area where the User may describe the administrative change. - `admin_Change_Date` (string,null) Date when the administrative change took place. - `admin_Change_Type` (string,null) Type of change that was made by Administration. 'Admin. Change Types' are configured within 'Grievance Configuration'. - `call_Key` (integer,null) ID of the call from which the grievance was submitted. - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `grievance_Category` (string,null) Category of the grievance. 'Greivance Categories' are configured within 'Grievance Configuration'. - `grievance_Filed` (string,null) Date when the grievance was viewed and filed by an Administartor. - `grievance_Received` (string,null) Date when the grievance was submitted. - `grievance_Resolved` (string,null) Date when the grievance was resolved. - `grievance_Source` (string,null) ID of the source of the grievance. - `grievance_Status` (string,null) Status of the grievance. 'Greivance Statuses' are configured within 'Grievance Configuration'. - `grievance_Type` (string,null) Type of the grievance. 'Grievance Types' are configured within 'Grievance Configuration'. - `issue` (string,null) Area where the User may describe the issue. - `issue_Date` (string,null) Date when the issue occurred. - `issue_Type` (string,null) Type of issue the grievance is associated with. 'Issue Types' are configured within 'Grievance Configuration'. - `member_Seq` (string,null) Sequential identifier of the Member associated with the grievance. - `patient_Account_Number` (string,null) Account number of the Patient associated with the grievance. - `provider_ID` (string,null) ID of the Provider associated with the grievance. - `resolution` (string,null) Area where the User may describe the resolution. - `resolution_Date` (string,null) Date when the resolution was implemented. - `resolution_Type` (string,null) Type of resolution used to address the grievance. 'Resolution Types' are configured within 'Grievance Configuration'. - `subscriber_ID` (string,null) Unique system assigned number for the Subscriber - `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