# Create an outgoing wire transfer in bulk

Submit the details for the creation of a batch of Outgoing Wire Transfers.

The bulkId returned in the response can subsequently be used to launch the execution of the bulk process through Execute Bulk Process. A submitted bulk process can be managed (executed, accessed, paused, resumed and cancelled) by any Authorised User of the same identity of the user that submits the details.

The status of the bulk process after execution of this operation is set to ‘SUBMITTED’. The execution of the bulk process is launched through the Execute bulk process operation.

The submission of data for a bulk process does not expire but it can be cancelled through Cancel Bulk Process.

The system is configured to accept bulk requests to process up to a maximum of 10,000 bulk operations.

Each individual operation in this bulk will be processed via Create an Outgoing Wire Transaction.

Endpoint: POST /bulks/outgoing_wire_transfers
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):

  - `pathParams` (object)

  - `requestBody` (object)

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

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

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

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

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

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

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

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

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

  - `requestBody.destinationBeneficiary` (any, required)

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

## Response 201 fields (application/json):

  - `bulkId` (string)

  - `operationCount` (integer)

  - `path` (string)