# Create or Update Batch PlanPreEx

Create or Update multiple PlanPreEx at once.  If the entity exists, it will be updated.  If the entity does not exist, it will be created.

Endpoint: PUT /plans/{planID}/pre-existing-coverages-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Path parameters:

  - `planID` (string, required)
    Plan ID

## Request fields (application/json):

  - `plan_ID` (string, required)
    References the Plans.Plan_ID value in parent table.

  - `coverage_Type` (string, required)
    Coverage type, based on enrollment, that will be applied by the pre-existing condition.

  - `disclosed_Ex_Code` (string,null)
    ExCode applied to this PlanPreEx disclosure.

  - `disclosed_From_Range` (integer,null)
    Holds the value of the lower bound of a range defined for disclosed pre-existing  entry.

  - `disclosed_Pre_Ex_Amount` (number,null)
    Amount allowed before a pend/deny on a pre-ex claim detail line, use in conjunction with Disclosed_Ex_Code.

  - `disclosed_Range_Type` (string,null)
    Defines the type of range used with the bounds of the disclosed range. D = Days, M = Months.

  - `disclosed_Thru_Range` (integer,null)
    Holds the value of the upper bound of a range defined for disclosed pre-existing  entry.

  - `entry_Date` (string)
    Date when the record was added to the system.

  - `entry_User` (string,null)
    User that first added the record to the system.

  - `ex_Code` (string,null)
    Ex Code associated with the pre-existing condition.

  - `from_Range` (integer,null)
    Beginning of the duration range that the pre-existing Conditon will apply to.

  - `pre_Ex_Amount` (number,null)
    Dollar amount that will be applied by the pre-existing condition before pending or denying claims.

  - `range_Type` (string,null)
    Unit of time used to measure the pre-existing Condition duration. Limited to units of either months or days.

  - `thru_Range` (integer,null)
    End of the duration range that the pre-existing Conditon will apply to.

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