# Create or Update Batch PayorAccount

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

Endpoint: PUT /payor-accounts-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Request fields (application/json):

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

  - `account_Key` (integer, required)
    References the FundingAccount.Account_Key associated with this Payor/Account. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `check_Stock` (integer,null)
    When a check is printed, the check will default to the selected check stock.

  - `currency_ID` (string,null)
    Identifies the currency that is used by the Payor.

  - `default_Contact_Method` (string,null)
    Identifies the desired default contact method of the Payor.

  - `default_Funding_Format` (string,null)
    Identifies the desired default funding format of the Payor.

  - `effective_Date` (string,null)
    Date when the Payor account becomes/became effective.

  - `entry_Date` (string)
    Date when the record was added to the system.

  - `entry_User` (string,null)
    User that first added the record to the system.

  - `ex_Code` (string,null)
    Allows the User to select an Ex Code that will be applied to any claims associated with the Payor whenever the 'Apply Ex Code' option is selected.

  - `funding_Threshold` (integer,null)
    This option is informational only.

  - `logo_File` (string,null)
    Displays the currently used logo file for the Payor. This logo can be applied to custom check stock.

  - `payor_ID` (string, required)
    References the Payor.Payor_ID associated with this Payor/Account.

  - `signatures_Required` (integer,null)
    This option is informational only.

  - `single_Check_Per_Claim` (boolean, required)
    Requires that this Payor's claims be paid for with a single check. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `term_Date` (string,null)
    Date when the Payor account becomes/became terminated.

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

## 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` (string,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