---
title: "Get a Connect balance transfer"
method: GET
path: "/v2/connect/balance-transfers/{balanceTransferId}"
tags: ["Balance Transfers API"]
---

# Get a Connect balance transfer

`GET /v2/connect/balance-transfers/{balanceTransferId}`

## Request

- Base URL: `https://api.mollie.com`
- URL: `https://api.mollie.com/v2/connect/balance-transfers/{balanceTransferId}`
- Auth: one of:
  - HTTP bearer
  - OAuth 2
    - Authorization code: `https://my.mollie.com/oauth2/authorize`
    - Token URL: `https://api.mollie.com/oauth2/tokens` scopes: `balance-transfers.read`

Retrieve a single Connect balance transfer object by its ID.

> 🔑 Access with
>
> [Advanced access token with **balance-transfers.read**](/reference/authentication)
>
> [OAuth access with **balance-transfers.read**](/reference/authentication)

## Query parameters

- `testmode` boolean

## Response `200`

The Connect balance transfer object.

- object
  - `resource` string, required: Indicates the response contains a balance transfer object. Will always contain the string `connect-balance-transfer` for this endpoint.
  - `id` string, required: The identifier uniquely referring to this balance transfer. Mollie assigns this identifier at balance transfer creation time. Mollie will always refer to the balance transfer by this ID. Example: `cbtr_j8NvRAM2WNZtsykpLEX8J`.
  - `amount` object, required: The amount to be transferred, e.g. `{"currency":"EUR", "value":"1000.00"}` if you would like to transfer €1000.00.
    - `currency` string, required: A three-character ISO 4217 currency code.
    - `value` string, required: A string containing an exact monetary amount in the given currency.
  - `source` object, required: A party involved in the balance transfer, either the sender or the receiver.
    - `type` string, required: Defines the type of the party. At the moment, only `organization` is supported. Possible values: `organization`
    - `id` string, required: Identifier of the party. For example, this contains the organization token if the type is `organization`.
    - `description` string, required: The transfer description for the transfer party. This is the description that will appear in the financial reports of the party.
  - `destination` object, required: A party involved in the balance transfer, either the sender or the receiver.
    - `type` string, required: Defines the type of the party. At the moment, only `organization` is supported. Possible values: `organization`
    - `id` string, required: Identifier of the party. For example, this contains the organization token if the type is `organization`.
    - `description` string, required: The transfer description for the transfer party. This is the description that will appear in the financial reports of the party.
  - `description` string, required: The transfer description for initiating party.
  - `status` string, required: The status of the transfer. Possible values: `created` `failed` `succeeded`
  - `statusReason` object, required: The reason for the current status of the transfer, if applicable.
    - `code` string, required: A machine-readable code that indicates the reason for the transfer's status. Possible values: `request_created` `success` `source_not_allowed` `destination_not_allowed` `insufficient_funds` `invalid_source_balance` `invalid_destination_balance` `transfer_request_expired` `transfer_limit_reached`
    - `message` string, required: A description of the status reason, localized according to the transfer.
  - `category` string: The type of the transfer. Different fees may apply to different types of transfers. Possible values: `invoice_collection` `purchase` `chargeback` `refund` `service_penalty` `discount_compensation` `manual_correction` `other_fee`
  - `metadata` object: A JSON object that you can attach to a balance transfer. This can be useful for storing additional information about the transfer in a structured format. Maximum size is approximately 1KB.
  - `createdAt` string, required: The entity's date and time of creation, in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format.
  - `executedAt` string, nullable: The date and time when the transfer was completed, in ISO 8601 format. This parameter is omitted if the transfer is not executed (yet).
  - `testmode` boolean: Whether to create the entity in test mode or live mode. You can enable test mode by setting `testmode` to `true`.
  - `mode` string, required: Whether this entity was created in live mode or in test mode. Possible values: `live` `test`

## Other responses

- `404`: No entity with this ID exists.
- `429`: Rate Limit has been reached.

---

[API](https://skmtc.dev/mollie/apis/mollie-connect.md) - [All operations](https://skmtc.dev/mollie/apis/mollie-connect/llms.txt) - [OpenAPI document](https://skmtc.dev/mollie/apis/mollie-connect/revisions/65271e79a786?raw)