# Create or Update Batch SubEnrollmentPlan

Create or Update multiple SubEnrollmentPlan 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/{groupID}/{divisionID}/{groupCoverageStart}/{startDate}/plans-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

  - `vbasoftware-database` (string, required)
    Target database

## Path parameters:

  - `subscriberID` (string, required)
    Subscriber ID

  - `groupID` (string, required)
    Group ID

  - `divisionID` (string, required)
    Division ID

  - `groupCoverageStart` (string, required)
    Group Coverage Start

  - `startDate` (string, required)
    Start Date

## Request fields (application/json):

  - `subscriber_ID` (string, required)
    References the Subenrollment.Subscriber_ID value in the parent table.

  - `group_ID` (string, required)
    References the Subenrollment.Group_ID value in the parent table.

  - `division_ID` (string, required)
    References the Subenrollment.Division_ID value in the parent table.

  - `group_Coverage_Start` (string, required)
    References the Subenrollment.Group_Coverage_Start value in the parent table. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `start_Date` (string, required)
    References the Subenrollment.Start_Date value in the parent table. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `plan_ID` (string, required)
    References the GroupContractPlan.Plan_ID value indicating which Plan this member is enrolling that is being offered.

  - `plan_Start` (string, required)
    Start date of Plan coverage. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `application_Received_Date` (string,null)
    Holds the date for the subscriber's application to disclose pre-existing conditions.

  - `dollar_Amount` (number,null)
    The Subscriber's 'Volume' within the selected plan on the enrollment. This will impact invoicing.

  - `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

  - `ltC_Daily_Benefit_Amount` (number,null)
    Member elected Daily Benefit Amount

  - `ltC_Lifetime_Max_Amount` (number,null)
    Lifetime Max Amount elected

  - `ltC_Lifetime_Max_Days` (integer,null)
    Lifetime Max Days elected

  - `ltC_Lifetime_Max_Years` (integer,null)
    Lifetime Max Years elected

  - `ltC_Monthly_Benefit_Amount` (number,null)
    Member elected Monthly Benefit Amount

  - `paid_Through` (string,null)
    Date that the premiums have been paid through for this plan. The 'Paid Thru Exceeded' Ex Code will be applied to Claims adjudicated with a service date beyond this date.

  - `plan_End` (string,null)
    End date of Plan coverage.

  - `reason_ID` (integer,null)
    This identifier the reason the plan was termed.

  - `tier` (string,null)
    The Subscriber's 'Tier' within the selected plan on the enrollment. This will impact adjudication and invoicing.

  - `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

  - `use_Volume_Scale` (boolean, required)
    This option tells the system to calculate the 'Volume' using the Group volume rules. Checking this box will display an elipsis that when clicked will explain the volume calculation. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `writing_CommissionAgencyRep_Key` (integer,null)
    Unique identifier for the CommissionAgencyRep table

## 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