---
title: "Perform several estimations in one request"
method: POST
path: "/orders/estimate/multiple"
tags: ["Orders"]
---

# Perform several estimations in one request

`POST /orders/estimate/multiple`

This endpoint is equivalent to `/orders/estimate` except that several estimations can be performed in a single request.

## Request body

- AmountEstimateRequest[]
  - union
    - InputAmountEstimateRequest
      - `fix_invalid_amount` boolean — When `true`, the server may adjust the specified amount and perform an estimation for that adjusted amount instead of returning an error response indicating that the specified amount is invalid. For instance, when this option is `true`, the server will correct an amount of "70.123 EUR" to "70.12 EUR". This option defaults to `false`. Regardless of the value of this option, the server may return an estimate for a different amount in case the specified amount is too large or too small.
      - `partner_fee` PartnerFee — -> An additional fee perceived on behalf of the partner placing the order, expressed as a factor of the amount received from the customer.
        - `factor` union, required
          - number
          - string
      - `purpose` OrderPurpose — Information about the purpose of the order.
        - `category` string — Non-exhaustive list of possible values: - `bill_payment`: The purpose of the order is to pay a bill.
        - `comment` string — Comment about the purpose of the order. Users can use this comment in order to remember what was their purpose when placing the order.
      - `input` InputAmountEstimateRequestInput, required — When `type` is not specified, it defaults to `"bank_account"` for fiat currencies and `"crypto_address"` for crypto currencies.
        - `currency` string, required
        - `type` 'bank_account' | 'bity_account' | 'crypto_address' | 'online_instant_payment' — Type of the input of an order. The enumeration is non-exhaustive.
      - `output` InputAmountEstimateRequestOutput, required — When `type` is not specified, it defaults to `"bank_account"` for fiat currencies and `"crypto_address"` for crypto currencies.
        - `currency` string, required
        - `type` 'bank_account' | 'bity_account' | 'crypto_address' — Type of the output of an order. The enumeration is non-exhaustive.
        - `amount` string, required — Decimal number. Output amount of the exchange; amount to be received by the output object. The output amount is all inclusive. Costs and fees are included.
    - OutputAmountEstimateRequest — Request an estimate of the output amount based on a specified input amount.
      - `fix_invalid_amount` boolean — When `true`, the server may adjust the specified amount and perform an estimation for that adjusted amount instead of returning an error response indicating that the specified amount is invalid. For instance, when this option is `true`, the server will correct an amount of "70.123 EUR" to "70.12 EUR". This option defaults to `false`. Regardless of the value of this option, the server may return an estimate for a different amount in case the specified amount is too large or too small.
      - `partner_fee` PartnerFee — -> An additional fee perceived on behalf of the partner placing the order, expressed as a factor of the amount received from the customer.
        - `factor` union, required
          - number
          - string
      - `purpose` OrderPurpose — Information about the purpose of the order.
        - `category` string — Non-exhaustive list of possible values: - `bill_payment`: The purpose of the order is to pay a bill.
        - `comment` string — Comment about the purpose of the order. Users can use this comment in order to remember what was their purpose when placing the order.
      - `input` OutputAmountEstimateRequestInput, required — When `type` is not specified, it defaults to `"bank_account"` for fiat currencies and `"crypto_address"` for crypto currencies.
        - `currency` string, required
        - `type` 'bank_account' | 'bity_account' | 'crypto_address' | 'online_instant_payment' — Type of the input of an order. The enumeration is non-exhaustive.
        - `amount` string, required — Decimal number. Input amount of the exchange; amount to be sent by the customer. The input amount is all inclusive. Costs and fees are included.
      - `output` OutputAmountEstimateRequestOutput, required — When `type` is not specified, it defaults to `"bank_account"` for fiat currencies and `"crypto_address"` for crypto currencies.
        - `currency` string, required
        - `type` 'bank_account' | 'bity_account' | 'crypto_address' — Type of the output of an order. The enumeration is non-exhaustive.

## Response `200`

Successful operation

- AmountEstimate[]
  - `input` AmountEstimateInput, required
    - `amount` string, required — Decimal number. Input amount of the exchange; amount to be sent by the customer. The input amount is all inclusive. Costs and fees are included.
    - `currency` string, required
    - `minimum_amount` string — Decimal number as a string
    - `object_information_optional` boolean — When true, indicates that it is not required to provide information about the object which is going to pay the order. In order to not provide information about the input object, do not include `bic_swift`, `crypto_address`, `iban`, `owner` and `type` in the input object.
    - `type` 'bank_account' | 'bity_account' | 'crypto_address' | 'online_instant_payment', required — Type of the input of an order. The enumeration is non-exhaustive.
  - `ordering_requirements` OrderingRequirements — Non-exhaustive list of requirements that need to be met in order to successfully place an order with parameters corresponding to the ones present in this response. Note that the list being non-exhaustive also means that the absence of a requirement in this list does not imply that the absent requirement is irrelevant.
    - `account` OrderingRequirementAccount — Usage of a Bity account is required.
      - `satisfied` boolean
    - `account_quota` OrderingRequirementAccountQuota — The amounts are suitable for the current Bity account quota.
      - `satisfied` boolean
    - `kyc` OrderingRequirementKyc — The Bity account has made sufficient progress through the KYC process.
      - `satisfied` boolean
  - `output` AmountEstimateOutput, required
    - `amount` string, required — Decimal number. Output amount of the exchange; amount to be received by the output object. The output amount is all inclusive. Costs and fees are included.
    - `currency` string, required
    - `minimum_amount` string — Decimal number as a string
    - `type` 'bank_account' | 'bity_account' | 'crypto_address', required — Type of the output of an order. The enumeration is non-exhaustive.
  - `price_breakdown` PriceBreakdown, required
    - `customer_trading_fee` object — The customer trading fee applied to this order.
      - `amount` string, required — Decimal number as a string
      - `currency` string, required
    - `instant_payment_fee` object — The instant payment fee applied to this order.
      - `amount` string, required — Decimal number as a string
      - `currency` string, required
    - `non-verified_fee` object — The non-verified fee applied to this order.
      - `amount` string, required — Decimal number as a string
      - `currency` string, required
    - `output_transaction_cost` object — Execution cost of the output transaction. Includes crypto transaction fees, bank transaction fees, etc.
      - `amount` string, required — Decimal number as a string
      - `currency` string, required
    - `partner_fee` object — -> Additional fee perceived on behalf of the partner having placed the order.
      - `amount` string, required — Decimal number as a string
      - `currency` string, required

## Other responses

- `400` — This endpoint can produce the same errors as `/orders/estimate` in addition to refusing to perform too many estimations in a single call.
- `429` — Rate-limited (request ignored)

---

[API](https://skmtc.dev/bity/apis/bity-exchange-api.md) · [All operations](https://skmtc.dev/bity/apis/bity-exchange-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/bity/bity-exchange-api/revisions/fd48443fbac2/schema)