# Create or Update Batch CredAttestationQuestion

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

Endpoint: PUT /credentialing-attestation-questions-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Request fields (application/json):

  - `credAttestationQuestion_Key` (integer, required)
    Unique Identity Key associated with this table. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `dateAnswer` (boolean, required)
    Identifies that the question requires a date answer. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `default_Method_Key` (integer,null)
    Specifies the default method that will be used to administer the question.

  - `default_Source_Key` (integer,null)
    Specifies the default source of the question.

  - `default_Type_Key` (integer,null)
    Specifies the default question type.

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

  - `numericAnswer` (boolean, required)
    Identifies that the question requires a numeric answer. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `question` (string,null)
    Displays the text of the question.

  - `textAnswer` (boolean, required)
    Identifies that the question requires a text answer. Note: This field is marked as NOT NULL in the database and therefore required by the API.

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

  - `yesNoAnswer` (boolean, required)
    Identifies that the question requires a yes or no answer. Note: This field is marked as NOT NULL in the database and therefore required by the API.

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