# Create or Update Batch NetworkProcedureCluster Create or Update multiple NetworkProcedureCluster at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /networks/{networkID}/procedure-clusters-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Path parameters: - `networkID` (string, required) Network ID ## Request fields (application/json): - `network_ID` (string, required) Unique identifier assigned to the network. - `procedure_Cluster` (string, required) Identifies the procedure cluster that is to be tied to the pricing rule. - `effective_Date` (string, required) Date when the pricing rule becomes/became effective. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `bill_Percent` (number,null) Used with the pricing claimrule, sets a value for the allowed amount to a percentage of the billed amount during adjudication. Subsequent claimrules may affect pricing. - `claim_Type` (string,null) Defines what type of claims the Network Procedure Cluster applies to - `context4Fg` (boolean, required) This option tells the pricing rule to reference pricing received from Context4. If this is unchecked, it allows the User to have the functionality without the Context4 hook. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `fee_Percent` (number,null) Specifies the fee percentage that is to be tied to the selected procedure cluster. Negative values will apply a discount. - `flat_Rate` (number,null) Used with the pricing claimrule, sets a value for the allowed amount during adjudication. Subsequent claimrules may affect pricing. - `term_Date` (string,null) Date when the pricing rule expires/expired. - `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