# Create or Update Batch ProviderCredAttestation

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

Endpoint: PUT /provider-credentialing/{providerCredKey}/attestations-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Path parameters:

  - `providerCredKey` (integer, required)
    ProviderCred Key

## Request fields (application/json):

  - `providerCredAttestation_Key` (integer, required)
    Unique identifier for each attestation question. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `answerDate` (string,null)
    Answer to the selected attestation question.

  - `answerNumeric` (integer,null)
    Answer to the selected attestation question.

  - `answerText` (string,null)
    Answer to the selected attestation question.

  - `answerYesNo` (boolean,null)
    Answer to the selected attestation question.

  - `credAttestationMethod_Key` (integer,null)
    Allows the User to select the method of the selected attestation question.

  - `credAttestationQuestion_Key` (integer, required)
    Allows the User to select a question from the available attestation questions. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `credAttestationSource_Key` (integer,null)
    Allows the User to select the source of the selected attestation question.

  - `credAttestationType_Key` (integer,null)
    Allows the User to select the type of the selected attestation question.

  - `entry_Date` (string)
    User that first added the record to the system.

  - `entry_User` (string,null)
    Date when the record was first added to the system.

  - `providerCred_Key` (integer, required)
    Associates these custom question values with the credentialing process (ProviderCred.ProviderCred_Key) Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `question_Date` (string,null)
    Identifies the date when the attestation question was administered.

  - `update_Date` (string)
    User that last updated the record in the system.

  - `update_User` (string,null)
    Date when the record was last updated 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