# Update ClaimBatchLog

Updates a specific ClaimBatchLog.

Endpoint: PUT /claim-batch-logs/{claimBatchLogKey}
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Path parameters:

  - `claimBatchLogKey` (integer, required)
    ClaimBatchLog Key

## Request fields (application/json):

  - `claimBatchLog_Key` (integer, required)
    No longer in use.  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.

  - `batch_Claim` (integer, required)
    No longer in use.  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.

  - `batch_Number` (integer, required)
    No longer in use.  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.

  - `entry_Date` (string)
    No longer in use.

  - `entry_User` (string,null)
    No longer in use.

  - `job_Key` (integer, required)
    No longer in use.  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.

  - `log_Action` (string,null)
    No longer in use.

  - `log_Date` (string,null)
    No longer in use.

  - `log_Message` (string,null)
    No longer in use.

  - `log_Result` (string,null)
    No longer in use.

  - `update_Date` (string)
    No longer in use.

  - `update_User` (string,null)
    No longer in use.

## Response 200 fields (text/plain):

  - `data` (object)

  - `data.claimBatchLog_Key` (integer, required)
    No longer in use.  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.

  - `data.batch_Claim` (integer, required)
    No longer in use.  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.

  - `data.batch_Number` (integer, required)
    No longer in use.  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.

  - `data.entry_Date` (string)
    No longer in use.

  - `data.entry_User` (string,null)
    No longer in use.

  - `data.job_Key` (integer, required)
    No longer in use.  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.

  - `data.log_Action` (string,null)
    No longer in use.

  - `data.log_Date` (string,null)
    No longer in use.

  - `data.log_Message` (string,null)
    No longer in use.

  - `data.log_Result` (string,null)
    No longer in use.

  - `data.update_Date` (string)
    No longer in use.

  - `data.update_User` (string,null)
    No longer in use.

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