# Create or Update Batch PremInvoice Create or Update multiple PremInvoice at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /premium-invoices-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Request fields (application/json): - `invoice_Key` (integer, required) Unique identifier for the Invoice Note: This field is marked as NOT NULL in the database and therefore required by the API. - `additional_Invoice_Level` (string,null) Specifies invoice level of additional invoices defined on the prem rate. - `bill_Address` (string,null) Address of the group or individual the Invoice is for - `bill_Address2` (string,null) Second line for the Address of the group or individual the Invoice is for - `bill_City` (string,null) City of the group or individual the Invoice is for - `bill_County_Code` (string,null) County of the group or individual the Invoice is for. - `bill_Name` (string,null) Name of the group or individual the Invoice is for - `bill_State` (string,null) State of the group or individual the Invoice is for - `bill_Zip_Code` (string,null) Zip Code of the group or individual the Invoice is for - `billing_Cycle_ID` (string,null) This is the Billing Cycle the invoice was gerenated for. - `billing_From` (string,null) First day of the Invoice period - `billing_Thru` (string,null) Last day of the Invoice period - `due_Date` (string,null) Due Date of the Invoice - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `finalized` (boolean, required) Finalized invoices cannot be changed Note: This field is marked as NOT NULL in the database and therefore required by the API. - `finalized_Date` (string,null) Date the Invoice was Finalized - `finalized_User` (string,null) User that Finalized the Invoice - `invoice_Date` (string,null) Date of the Invoice - `invoice_Level` (string,null) Level of the Invoice: Group, Division, or Subscriber - `invoice_Number` (string,null) Number assigned to this Invoice - `invoice_Status` (string,null) Status of the Invoice: Open or Closed - `original_Invoice_Key` (integer,null) Identifies the Invoice that this Invoice was created from - `pay_Period` (integer,null) This number represents sequence of the payroll from the beginning of the payroll year. - `update_Date` (string) Date 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