# Create or Update Batch SubEnrollment Create or Update multiple SubEnrollment at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /subscribers/{subscriberID}/enrollments-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Path parameters: - `subscriberID` (string, required) Subscriber ID ## Request fields (application/json): - `subscriber_ID` (string, required) References Subscribers.Subscriber_ID value on the parent record. - `group_ID` (string, required) References the GroupContract.Group_ID value in the parent table. - `division_ID` (string, required) References the GroupContract.Division_ID value in the parent table. - `group_Coverage_Start` (string, required) References the GroupContract.Coverage_Start value in the parent table. - `start_Date` (string, required) Start date of Subenrollment coverage. - `annual_Max` (number,null) Annual maximum for identified policy. [Informational Only] - `date_Employed` (string,null) Start date of the Subscriber's employment. - `eligibility_Date` (string,null) Date the Subscriber was eligible for coverage. - `end_Date` (string,null) End date of Subenrollment coverage. - `entry_Date` (string) Date when the record was first added to the system. - `entry_User` (string,null) User that first added the record to the system. - `lifetime_Max` (number,null) Lifetime maximum for indentified policy. [Informational Only] - `original_Enrollment_Date` (string,null) Identifies the date the Enrollment began. This is useful if a new Group is added and insured Members have been covered under the Group Plan earlier than their start date with you. - `paid_Through` (string,null) Date that the premiums have been paid through. This field will auto populate with the most recent closed invoice ‘Bill Thru’ date if 'Set Paid Thru' is set through the Control Panel. The 'Paid Thru Exceeded' Ex Code will be applied to Claims adjudicated with a service date beyond this date. - `policy_Number` (string,null) Policy number issued from Insurer. [Informational Only] - `term_Date` (string,null) Termination date of the Subscriber's employment. - `update_Date` (string) Date when 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