---
title: "List Transactions for an Extended Preauthorization"
method: GET
path: "/v2.01/{ClientId}/extended-preauthorizations/{ExtendedPreauthorizationId}/transactions"
tags: ["Transactions"]
---

# List Transactions for an Extended Preauthorization

`GET /v2.01/{ClientId}/extended-preauthorizations/{ExtendedPreauthorizationId}/transactions`

## Request

- Base URL: `https://api.sandbox.mangopay.com`
- URL: `https://api.sandbox.mangopay.com/v2.01/{ClientId}/extended-preauthorizations/{ExtendedPreauthorizationId}/transactions`
- Auth: HTTP bearer

This call returns all preauthorized pay-ins, both captures and complements, made against a given extended preauthorization, whether they were successful or not.

## Path parameters

- `ClientId` string, required
- `ExtendedPreauthorizationId` string, required

## Query parameters

- `Status` string
- `ResultCode` string
- `BeforeDate` integer
- `AfterDate` integer

## Response `200`

Success

- ListTransactionsResponse
  - `Array (Transactions)` ListTransactionsResponseArrayTransactionsItems[]: The list of transactions created by the platform.
    - `Object (transaction)` TransactionResponse
      - `Id` string: Max length: 128 characters (see [data formats](/api-reference/overview/data-formats) for details) The unique identifier of the object.
      - `Tag` string: Max. length: 255 characters Custom data that you can add to this object, such as unique identifiers in your system. To store multiple values, you can serialize them into a single string, for example a JSON object: `"{\"id_1\":AB123,\"id_2\":DE456}"`.
      - `CreationDate` integer: Unix timestamp (UTC) of the date and time the object was created.
      - `AuthorId` string: The unique identifier of the user at the source of the transaction.
      - `CreditedUserId` string: **Default value:** The unique identifier of the owner of the credited wallet. The unique identifier of the user whose wallet is credited.
      - `DebitedFunds` TransactionResponseDebitedFunds: Information about the debited funds.
        - `Currency` string: **Allowed values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings). The currency of the amount.
        - `Amount` integer: The amount of the currency in its minor unit. For example, EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`.
      - `CreditedFunds` TransactionResponseCreditedFunds: Information about the credited funds (`CreditedFunds` = `DebitedFunds` - `Fees`).
        - `Currency` string: **Allowed values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings). The currency of the amount.
        - `Amount` integer: The amount of the currency in its minor unit. For example, EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`.
      - `Fees` TransactionResponseFees: Information about the fees taken by the platform for this transaction (and hence transferred to the Fees Wallet).
        - `Currency` string: **Allowed values:** The three-letter <a href="/api-reference/overview/data-formats" target="_blank">ISO 4217 code</a> (EUR, GBP, etc.) of a <a href="/guides/currencies" target="_blank">supported currency</a> (depends on feature, contract, and activation settings). The currency of the amount.
        - `Amount` integer: The amount of the currency in its minor unit. For example, EUR 12.60 would be represented as `1260` whereas JPY 12 would be represented as just `12`.
      - `Status` string: **Returned values:** `CREATED`, `SUCCEEDED`, `FAILED` The status of the transaction.
      - `ResultCode` string: The code indicating the result of the operation. This information is mostly used to <a href="/errors/codes">handle errors</a> or for filtering purposes.
      - `ResultMessage` string: The explanation of the result code.
      - `ExecutionDate` integer: Unix timestamp (UTC) of the date and time the status changed to `SUCCEEDED`, indicating that the transaction occurred. The statuses `CREATED` and `FAILED` return an `ExecutionDate` of `null`.
      - `Type` string: **Returned values:** `PAYIN`, `TRANSFER`, `CONVERSION`, `PAYOUT` The type of the transaction.
      - `Nature` string: **Returned values:** `REGULAR`, `REPUDIATION`, `REFUND`, `SETTLEMENT` The nature of the transaction, providing more information about the context in which the transaction occurred: - `REGULAR` – Relative to most of the transactions (pay-ins, payouts, and transfers) in a usual workflow. - `REPUDIATION` – Automatic withdrawal of funds from the platform's repudiation wallet as part of the dispute process (when the user has requested a chargeback). - `REFUND` – Reimbursement of a transaction to the user (pay-in refund), to a wallet (transfer refund), or of a payout (payout refund, only initiated by Mangopay). - `SETTLEMENT` – Transfer made to the repudiation wallet by the platform to settle a lost dispute.
      - `CreditedWalletId` string: The unique identifier of the credited wallet.
      - `DebitedWalletId` string: The unique identifier of the debited wallet.

## Changes

- **2026-10-01** `33a23ba84cdd`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/mangopay/apis/api-reference/changes/v2.01/:ClientId/extended-preauthorizations/:ExtendedPreauthorizationId/transactions/get.md)

---

[API](https://skmtc.dev/mangopay/apis/api-reference.md) - [All operations](https://skmtc.dev/mangopay/apis/api-reference/llms.txt) - [OpenAPI document](https://skmtc.dev/mangopay/apis/api-reference/revisions/d288c2f6fa97?raw)