# Create or Update Batch of Benefits

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

Endpoint: PUT /benefits-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Request fields (application/json):

  - `benefit_Code` (string, required)
    Unique identifier assigned to the Benefit Code.

  - `allow_Flat_Tax` (boolean, required)
    This option allows the User to enter a 'Flat Amt.' within the 'Financial' screen from the Member 'Details' drop-down menu. If this option is not selected, the 'Flat Tax' amount will default to zero when calculating disability payments. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `benefit_Category` (string,null)
    References the BenefitCategory.Benefit_Category table.

  - `benefit_Description` (string,null)
    Description of the associated Benefit Code.

  - `default_Unit_Type` (string,null)
    No longer in use.

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

  - `hipaA_Code` (string,null)
    HIPAA code associated with the specified Benefit. 835's require a maped HIPAA code on claims that pay less than the billed amount.

  - `invalid_Diag_Ex_Code` (string,null)
    No longer in use.

  - `invalid_Procedure_Ex_Code` (string,null)
    No longer in use.

  - `invalid_Prov_Type_Ex_Code` (string,null)
    No longer in use.

  - `invalid_Specialty_Ex_Code` (string,null)
    No longer in use.

  - `medicare` (string, required)
    No longer in use. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `pend_Ex_Code` (string,null)
    The Ex Code to apply when adjudicating a claim that has this benefit if the Pend_Flag is on.

  - `pend_Flag` (string, required)
    Whether or not to apply the Pend_Ex_Code value when adjudicating a claim that has this benefit.

  - `require_Type_Of_Svc` (string,null)
    No longer in use.

  - `update_Date` (string)
    Date when the record was last updated.

  - `update_User` (string,null)
    User that last updated the record.

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