# Create or Update Batch GroupUCPercent

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

Endpoint: PUT /groups/{groupID}/uc-percent-settings-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Path parameters:

  - `groupID` (string, required)
    Group ID

## Request fields (application/json):

  - `groupUCPercent_Key` (integer, required)
    Unique identifier for each UC Percent configuration for this Group. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `claim_Type` (string, required)
    Claim type that the UC percent settings will be applied to.

  - `custom_Percent` (number,null)
    Identifies the custom percentage that will be applied by the UC percent settings.

  - `custom_Percent_Claim_Type` (string,null)
    When using a custom percent, this applies a claim type restriction to the rule limiting which claim types can have UC applied.

  - `effective_Date` (string,null)
    Date when the UC percent settings become/became effective.

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

  - `fee_Sched` (string,null)
    When a fee schedule is used as the rate structure than the UC tables.

  - `group_ID` (string, required)
    References the Groups.Group_ID value on the parent record.

  - `term_Date` (string,null)
    Date when the UC percent settings expire/expired.

  - `uC_Percent` (string,null)
    Allows the User to select a default percentage that will be applied by the UC percent settings.

  - `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_Custom_Percent` (boolean, required)
    Allows the User to build a custom percentage for the UC percent settings instead of using one of the default percentages. Note: This field is marked as NOT NULL in the database and therefore required by the API.

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