# Create or Update Batch TimelyFiling Create or Update multiple TimelyFiling at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /timely-filings-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Request fields (application/json): - `timelyFiling_Key` (integer, required) Kev value identifying a specific timely filing record Note: This field is marked as NOT NULL in the database and therefore required by the API. - `claim_Type` (string,null) Specifies which claim type the timely filing conditions apply to - `date_Type` (string,null) Specifies which claim dates are used for timely filing - `description` (string,null) Description of the timely filing conditions - `division_ID` (string,null) ID of the division that the timely filing conditions apply to - `effective_Date` (string,null) Date the timely filing conditions become effective - `entry_Date` (string) Date record was first added to the system - `entry_User` (string,null) User that first added the record to the system - `ex_Code` (string,null) Ex code that is applied when timely filing conditions are met - `federal_ID` (string,null) Federal ID of the provider that the timely filing conditions apply to - `group_ID` (string,null) ID of the group that the timely filing conditions apply to - `inpatient` (boolean, required) Flag specifying if the timely filing applies to inpatient claims Note: This field is marked as NOT NULL in the database and therefore required by the API. - `network_ID` (string,null) ID of the network that the timely filing conditions apply to - `plan_ID` (string,null) ID of the plan that the timely filing conditions apply to - `provider_ID` (string,null) ID of the provider that the timely filing conditions apply to - `schedule_Custom` (string,null) Field specifying how the custom schedule type is defined - `schedule_Frequency` (integer,null) Number of days, months or years specified by the frequency - `schedule_Type` (string,null) Type of the schedule frequency, specifically day, month, year or custom - `term_Date` (string,null) Date the timely filing conditions terminate - `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