---
title: "List transactions for a delegation"
method: GET
path: "/delegation/{delegationId}/transactions"
tags: ["Delegation"]
---

# List transactions for a delegation

`GET /delegation/{delegationId}/transactions`

## Request

- Base URL: `https://api.sandbox.nevermined.app/api/v1`
- URL: `https://api.sandbox.nevermined.app/api/v1/delegation/{delegationId}/transactions`
- Auth: HTTP bearer

Returns a paginated list of charge transactions recorded against a delegation owned by the authenticated user. Requires a Nevermined API key.

## Path parameters

- `delegationId` string, uuid, required

## Query parameters

- `page` integer
- `offset` integer

## Response `200`

- DelegationTransactionListDto
  - `totalResults` number, required
  - `page` number, required
  - `offset` number, required
  - `transactions` DelegationTransactionDto[], required
    - `id` string, required
    - `delegationId` string, required
    - `providerTransactionId` string, required
    - `amountCents` string, required
    - `currency` string, required
    - `status` string, required
    - `failureReason` string, nullable, required
    - `feeCents` string, required: Nevermined’s routing fee for this charge, in cents, already INCLUDED in `amountCents`. Charged only on payments routed to an external merchant via the Router — `"0"` on every other row (a plan purchase on the card rails, or a crypto settlement), where no routing fee applies. On a Router row `amountCents - feeCents` is the merchant leg — **unless `feeReleased` is `true`, in which case `amountCents` is ALREADY net of the fee and must not be reduced again**. On other rows the identity does not hold either, because a plan purchase can carry a platform margin taken out of the price that this figure does not describe. **`"0"` does not by itself mean no fee applied:** the two figures round in opposite directions, so a fee too small to add a cent to the reserve still shows here as `"0"`. Read `feeAtomic` to answer that.
    - `feeAtomic` string, required: The same fee in the settlement asset’s smallest unit, rounded down. This is the field that answers “did a routing fee apply at all” — `"0"` means none did. The asset it is denominated in is the one the Router settled, reported on `GET /router/payments`; it is NOT the same unit as `amountCents`.
    - `feeBps` number, required: The fee rate applied, in basis points over a 10,000 denominator. Pinned per row, so a later rate change never rewrites what an old payment was charged. `0` when no fee applied.
    - `feeReleased` boolean, required: True when the routing fee was not collected and has been credited back to your cap. Non-delivery by the merchant is one cause; a fee leg that was refused, or expired before it could be broadcast, is another — so this does NOT mean the merchant failed you. **`amountCents` has ALREADY been reduced by `feeCents` when this is true**, so do not subtract the fee a second time. It does not follow that the remainder is the merchant leg: a payment whose merchant reserve was also released has that deducted from the same field and reads `status: 'failed'`. A fee too small to reserve a cent is released without ever setting this flag, so a row may read `false` here while `GET /router/payments` reports the fee `Released`; `amountCents` is untouched in that case, so the arithmetic above still holds.
    - `createdAt` string, date-time, required

## Other responses

- `404`: Delegation not found

---

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