# Create or Update Batch Event Create or Update multiple Event at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /events-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Request fields (application/json): - `event_ID` (integer, required) ID of the event. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `claim_Audit_Event` (boolean, required) Flag to indicate if the event triggers a Claim Audit. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `completion_Date` (string,null) Date the Event was Completed. - `completion_Percent` (number,null) Current Percentage that the Event has Completed - `due_Date` (string,null) Due Date of the Event - `end_Date` (string,null) End Date of the Event - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `event_Processor` (string,null) Object used when processing the event - `event_Type` (string,null) Identifier for the type of event - `meta_Data` (string,null) Meta data pertaining to the overall event - `next_Scheduled_Date` (string,null) Date when the 'Assigned User' will receive the next event reminder. - `next_Scheduled_Time` (string,null) Date when the event is due. - `priority` (string,null) Indicates the level of priority being assigned to the event. - `process_Automation_Event` (boolean, required) Flag to indicate if the event triggers a Report Series. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `reminder` (boolean, required) Indicates that the 'Assigned User' should receive a reminder regarding the event. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `reminder_Event_ID` (integer,null) Event ID of the Reminder - `reportSeries_Key` (integer,null) The key of the Report Series this Event trigger. - `start_Date` (string,null) Start Date of the Event - `status` (string,null) Identifies the current status of the event. - `subject` (string,null) Description of the event subject. - `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 - `userGroup_Key` (integer,null) Key value identifying the User Group to whom the event is assigned - `user_ID` (string,null) ID of the User to whom the event is assigned. ## 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