# Create a bulk of send transactions (deprecated)

Deprecated in favour of the Operations in Bulk.

Sends funds between multiple managed accounts and managed cards belonging to different corporate or consumer identities.

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

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

  - `sends` (array, required)
    The object representing the sends' details.

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

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

  - `sends.source` (object, required)

  - `sends.source.id` (string, required)

  - `sends.source.type` (string, required)
    Enum: "managed_cards", "managed_accounts"

  - `sends.destination` (any, required)

  - `sends.destinationAmount` (object, required)
    The object representing a monetary amount in a particular currency.

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

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

  - `sends.description` (string)
    The description details that are passed to the beneficiary.

  - `sends.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 a send 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.source` (object, required)

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

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

  - `response.destination` (any, required)

  - `response.destinationAmount` (object, required)
    The object representing a monetary amount in a particular currency.

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

  - `response.destinationAmount.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)
    The description details that are passed to the beneficiary.

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