# Create a bulk of outgoing wire transfer transactions (deprecated)

Deprecated in favour of the Operations in Bulk.

Transfers funds from multiple managed accounts to multiple external bank accounts.

The Outgoing Wire Transfer Profile (configured in the Multi Portal) specified determines the behaviour and restrictions of the transaction (for example, fees).

Note that even if the transaction is created successfully, you still need to check its state in order to determine if it is pending completion of an authentication challenge by the user.

Endpoint: POST /outgoing_wire_transfers/bulk/create
Version: 3.63.5
Security: auth_token, api-key

## Header parameters:

  - `idempotency-ref` (string)
    A unique call reference generated by the caller that, taking into consideration the payload as well as the operation itself, helps avoid duplicate operations. Idempotency reference uniqueness is maintained for at least 24 hours.

## Request fields (application/json):

  - `outgoingWireTransfers` (array, required)
    The object representing the outgoing wire transfers' details.

  - `outgoingWireTransfers.profileId` (string, required)
    The profile Id which a specific identity, instrument or transaction type is linked to.

Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.

You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.

Profile Ids can be found in the Multi Portal, in the API Credentials page.

  - `outgoingWireTransfers.tag` (string)
    The tag field is a custom field that can be used to search and filter.

  - `outgoingWireTransfers.sourceInstrument` (object, required)
    The managed account from which funds will be collected.

  - `outgoingWireTransfers.sourceInstrument.type` (string, required)
    Enum: "managed_accounts"

  - `outgoingWireTransfers.sourceInstrument.id` (string, required)

  - `outgoingWireTransfers.transferAmount` (object, required)
    The amount, in same currency as source and destination, that was transferred from the source.

  - `outgoingWireTransfers.transferAmount.currency` (string, required)
    The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.

  - `outgoingWireTransfers.transferAmount.amount` (integer, required)
    The monetary amount, scaled to the lowest denomination of the currency.

Example, an amount of 1000 for a EUR currency is actually 1000 Euro cents or EUR 10.00.

  - `outgoingWireTransfers.description` (string)
    These details are passed to the beneficiary as the reference . This field is mandatory for wire transfers executed over SEPA. The allowed length is dependent on the payment type:

SEPA <= 35 characters. An extended character set is accepted to cater for all European languages. If SEPA does not support a particular character, it is automatically converted to an acceptable alternative, in line with SEPA scheme guidance.

Faster Payments <= 18 characters

  - `outgoingWireTransfers.destinationBeneficiary` (any, required)

  - `outgoingWireTransfers.scheduledTimestamp` (string)
    The epoch timestamp at which the transaction is scheduled to be executed.

## Response 200 fields (application/json):

  - `response` (array, required)

  - `response.id` (string)
    The unique identifier of an outgoing wire transfer transaction.

  - `response.profileId` (string, required)
    The profile Id which a specific identity, instrument or transaction type is linked to.

Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.

You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.

Profile Ids can be found in the Multi Portal, in the API Credentials page.

  - `response.tag` (string)
    The tag field is a custom field that can be used to search and filter.

  - `response.sourceInstrument` (object, required)
    The managed account from which funds will be collected.

  - `response.sourceInstrument.type` (string, required)
    Enum: "managed_accounts"

  - `response.sourceInstrument.id` (string, required)

  - `response.transferAmount` (object, required)
    The amount, in same currency as source and destination, that was transferred from the source.

  - `response.transferAmount.currency` (string, required)
    The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.

  - `response.transferAmount.amount` (integer, required)
    The monetary amount, scaled to the lowest denomination of the currency.

Example, an amount of 1000 for a EUR currency is actually 1000 Euro cents or EUR 10.00.

  - `response.description` (string)
    These details are passed to the beneficiary as the reference . This field is mandatory for wire transfers executed over SEPA. The allowed length is dependent on the payment type:

SEPA <= 35 characters. An extended character set is accepted to cater for all European languages. If SEPA does not support a particular character, it is automatically converted to an acceptable alternative, in line with SEPA scheme guidance.

Faster Payments <= 18 characters

  - `response.destinationBeneficiary` (any, required)

  - `response.scheduledTimestamp` (string)
    The epoch timestamp at which the transaction is scheduled to be executed.

## Response 400 fields (application/json):

  - `message` (string)
    When present helps to identify and fix the problem.

  - `syntaxErrors` (object)
    Is returned as part of an HTTP error response whenever a syntax error is detected. A list of the fields together with their syntax error will be provided.

  - `syntaxErrors.invalidFields` (array)

  - `syntaxErrors.invalidFields.params` (array)

  - `syntaxErrors.invalidFields.fieldName` (string)

  - `syntaxErrors.invalidFields.error` (string)
    Enum: "REQUIRED", "HAS_TEXT", "REQUIRES", "SIZE", "RANGE", "IN", "NOT_IN", "REGEX", "EXACTLY", "AT_LEAST", "AT_MOST", "ALL_OR_NONE"

## Response 409 fields (application/json):

  - `errorCode` (string, required)
    Error codes:
  * TRANSACTION_LIMIT_EXCEEDED - The number of transactions exceeds the limit of 1000.
    Enum: "TRANSACTION_LIMIT_EXCEEDED"

## Response default fields (application/json):

  - `code` (string)

  - `message` (string)


## Response 401 fields

## Response 403 fields

## Response 429 fields

## Response 500 fields

## Response 503 fields