# Create or Update Batch IPWhitelist

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

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

## Header parameters:

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

## Request fields (application/json):

  - `ipWhitelist_Key` (integer, required)
    Identity key for the record.  Note: The database will apply a default value of 0 for this field if a value is not provided.  This field is also marked as NOT NULL in the database and therefore required by the API.  If you do not have a value for this field, supply the database default value of 0 to meet the API requirements and ensure that the functionality occurs as expected.

  - `description` (string, required)
    User-defined description for the record to help identify the reason for usage.

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

  - `iP_Address` (string, required)
    IP Address that will be whitelisted for accessing the APIs. This field supports both single IPv4 addresses and CIDR blocks for specifying IP ranges. 

- Single IP Address: Provide a specific IPv4 address (e.g., "192.168.1.1") to whitelist that single address.
- CIDR Block: Provide a CIDR block (e.g., "192.168.1.0/24") to whitelist a range of addresses. 
            
Notes:
- The value must be unique within the whitelist.
- The maximum length of this field is 39 characters to accommodate IPv4 addresses and CIDR notation.
- Ensure that the provided IP address or CIDR block is correctly formatted to avoid validation errors.

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