# Create or Update Batch MemberAccount

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

Endpoint: PUT /subscribers/{subscriberID}/members/{memberSeq}/accounts-batch
Version: v1
Security: apiKeyAuth, bearerAuth

## Header parameters:

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

## Path parameters:

  - `subscriberID` (string, required)
    Subscriber ID

  - `memberSeq` (string, required)
    Member Seq

## Request fields (application/json):

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

  - `account_Key` (integer,null)
    References FundingAccount.Account_Key for this account on this Member.

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

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

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

  - `member_Seq` (string,null)
    References Members.Member_Seq value on the parent record.

  - `preNote_Sent` (boolean, required)
    Custom value used for accounting system integrations. Note: This field is marked as NOT NULL in the database and therefore required by the API.

  - `preNote_SentDate` (string,null)
    Custom value used for accounting system integrations.

  - `subscriber_ID` (string,null)
    References Members.Subscriber_ID value on the parent record.

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

  - `wire_Transfer` (boolean, required)
    Indicates that the Member account is setup for direct deposit. Checking this box will activate the ACH option within Subscriber Information. 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