---
title: "List earmarks (Pismo account ID)"
method: GET
path: "/cash-management/v1/earmarks"
tags: ["Earmarking (Pismo account ID)"]
---

# List earmarks (Pismo account ID)

`GET /cash-management/v1/earmarks`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/cash-management/v1/earmarks`
- Auth: HTTP bearer

List all created earmarks, including ones that are canceled or have already been executed.

## Query parameters

- `cursor` string
- `limit` integer
- `balanceGt` number, float
- `balanceGe` number, float
- `balanceLt` number, float
- `balanceLe` number, float

## Response `200`

OK

- ListEarmarksResponse
  - `earmarks` EarmarkResponse[]: List of earmarks
    - `earmark_id` string: Earmark ID. Used as the primary key for query and update operations. It has the same value as the tracking ID, if one is provided. Generated by [Create Earmark](https://developers.pismo.io/pismo-docs/reference/post-corporate-v2-earmarks).
    - `account_id` integer: Account ID generated by [Create Corporate Account](https://developers.pismo.io/pismo-docs/reference/post-account).<br> `minimum: 1`
    - `external_account_id` string: External ID of the account on which the earmark is created. Should be the same `external_account_id` that was used to log in. Should be the same `external_account_id` used in [Create Corporate Account](https://developers.pismo.io/pismo-docs/reference/post-account).
    - `description` string: Earmark description
    - `amount` number, float: Earmark amount<br> `minimum: 0.01` `maximum: 18446744073709551617`
    - `balance` number: Earmark balance. Initially equal to the earmarked amount and decreases as the reserved funds are used up or decreased in a decrease operation. It can also increase if an increase operation is performed.<br> `minimum: 0` `maximum: 18446744073709551617`
    - `release_datetime` string, date-time: RFC 3339 date/time for earmark release. Used to schedule a cash-out (usually a payment) at the specified release date and time. At `release_datetime`, an automatic process releases the earmarked funds and settles the cash-out. If no `release_datetime` is set, the earmarked amount is held indefinitely until the customer cancels the earmark.
    - `internal_operations` InternalOperation[]: List of internal operations performed to hold or release the earmark funds.
      - `tracking_id` string, required: A unique payment tracking number provided by the client. If an existing `tracking_id` is found on the Pismo platform, the API returns a `409` error. This field is: * Unique within the organization * Immutable: It can't be updated * Not recyclable: You can't reuse a `tracking_id`
      - `business_date` string, date: Specifying a `business_date` value impacts the account balance history.<br> <b>Notes</b>: - The business date is in ISO 8601 format. - The business date allows users to designate the balance history cycle in which a payment is posted. - You can specify a `business_date` within the current working day or up to one working day before or after.
      - `type` 'HOLD_FUNDS' | 'RELEASE_FUNDS' | 'INCREASE' | 'DECREASE': Internal operation type.<br> `minLength: 1` `maxLength: 13`
      - `processing_code` string: Processing code used to create the underlying transaction. Each internal operation type uses a default processing code.<br> `minLength: 1` `maxLength: 6`
      - `amount` number: Internal operation amount<br> `minimum: 0` `maximum: 18446744073709551617`
      - `validation_rules` ValidationRules: Rules that determine which validations are executed during the payment process.<br> Available validation rules: - `LEDGER` - `ACCOUNT_STATUS` - `FLEX_CONTROLS` - `RATES`<br> `force` is only supported for `LEDGER`. `override` is supported for `ACCOUNT_STATUS`, `FLEX_CONTROLS`, and `RATES`.
      - `created_at` string, date-time: Internal operation creation time. Format = yyyy-mm-dd:hr:mm:ss.
      - `metadata` InternalOperationMetadata: Key-value pairs containing data intended for storage in the Pismo system.<br> **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](ref:get-started-with-pismo-apis).
  - `pagination` Pagination: Data related to list pagination using a cursor.
    - `limit` integer: Maximum number of items per page
    - `cursor` string: Cursor pointing to the next page of results

## Other responses

- `400`: Bad Request
- `401`: Access token is missing or invalid
- `403`: The request has been lost
- `500`: Internal Server Error

---

[API](https://skmtc.dev/pismo/apis/banking-transaction-banking.md) - [All operations](https://skmtc.dev/pismo/apis/banking-transaction-banking/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/banking-transaction-banking/revisions/1334306c9303?raw)