> ## Documentation Index > Fetch the complete documentation index at: https://docs.dimepayments.com/llms.txt > Use this file to discover all available pages before exploring further. # List releasable transactions > The payments of a held-funds merchant that can be released right now, and what each comes to — the list to choose from when releasing by `transaction_info_ids`. A payment is listed once the processor has reported it funded (usually the next day), is past the ACH return window if it is ACH, has had no refund, return or chargeback, and has not already been released. `amount` is its net amount less any split owed on it. Newest first, up to 500; `truncated` says whether there are more. A payment being listed here does not guarantee it can be released on its own: every release is also capped by `releasable` on *Get held balance*. ## OpenAPI ````yaml https://app.dimepayments.com/openapi.yaml get /api/funds/transactions openapi: 3.0.3 info: title: Dime Payments API Documentation description: >- A simple, basic API for managing Merchants through Dime Payments. JSON based REST API version: 1.0.0 servers: - url: https://app.dimepayments.com security: - default: [] tags: - name: Merchant management description: '' - name: Transaction management description: >- APIs for managing transactions. Depending on API KEY permissions, one should be able to charge credit cards, ACH, Google/Apple Pay wallets along with other functions. - name: Chargeback management description: '' - name: Document management description: '' - name: Addresses description: |- APIs for managing customer addresses - name: Customer management description: >- APIs for managing customers. Depending on API KEY permissions, one should be able to list, create, update, and delete customers along with several other customer specific requests. - name: Deposit management description: '' - name: Held funds description: '' - name: Invoice management description: >- APIs for managing invoices. Depending on API KEY permissions, one should be able to list, create, update, delete, and send invoices, manage their line items, and manage recurring-invoice schedules. Every request is scoped to a single Merchant via the required `data.sid`. - name: Payment Method management description: >- APIs for managing payment methods associated with customers. Depending on API KEY permissions, one should be able to list, show, create, update, and delete payment methods. - name: Recurring Payments management description: >- APIs for managing recurring payments. Depending on API KEY permissions, one should be able to create, edit, pause, cancel along with other functions. - name: Subscription Plans management description: >- Merchant-facing API for subscription plans (recurring offerings customers subscribe to). The merchant is identified by `data.sid`; the token must carry the matching `subscription-plan:*` ability. Mirrors the recurring-payment and invoice API controllers. - name: Subscriptions management description: >- Merchant-facing API for individual customer subscriptions (enrollments in a plan). The merchant is identified by `data.sid`; the token must carry the matching `subscription:*` ability. Lifecycle transitions delegate to the {@see \App\Actions\Subscription} action classes so the matching `SUBSCRIPTION_*` webhook always fires. Mirrors the recurring-payment and subscription-plan API controllers. - name: Zapier description: >- APIs for use through Zapier. Depending on API KEY permissions, one should be able to see customers and transactions data. paths: /api/funds/transactions: get: tags: - Held funds summary: List releasable transactions description: >- The payments of a held-funds merchant that can be released right now, and what each comes to — the list to choose from when releasing by `transaction_info_ids`. A payment is listed once the processor has reported it funded (usually the next day), is past the ACH return window if it is ACH, has had no refund, return or chargeback, and has not already been released. `amount` is its net amount less any split owed on it. Newest first, up to 500; `truncated` says whether there are more. A payment being listed here does not guarantee it can be released on its own: every release is also capped by `releasable` on *Get held balance*. operationId: listReleasableTransactions parameters: [] requestBody: required: false content: application/json: schema: type: object properties: data: type: object description: '' example: [] properties: sid: type: string description: The ID of the merchant. example: '91828382' required: - sid responses: '200': description: Success content: application/json: schema: type: object example: data: sid: '91828382' transactions: - transaction_info_id: '1297431' type: CC transaction_date: '2026-09-28T15:12:09+00:00' gross_amount: 100 net_amount: 97 split_amount: 1.25 amount: 95.75 total: 95.75 truncated: false properties: data: type: object properties: sid: type: string example: '91828382' transactions: type: array example: - transaction_info_id: '1297431' type: CC transaction_date: '2026-09-28T15:12:09+00:00' gross_amount: 100 net_amount: 97 split_amount: 1.25 amount: 95.75 items: type: object properties: transaction_info_id: type: string example: '1297431' type: type: string example: CC transaction_date: type: string example: '2026-09-28T15:12:09+00:00' gross_amount: type: integer example: 100 net_amount: type: integer example: 97 split_amount: type: number example: 1.25 amount: type: number example: 95.75 total: type: number example: 95.75 description: The sum of `amount` across the list. truncated: type: boolean example: false description: >- True when there are more than 500 and only the newest are listed. '401': description: Incorrect API Key Permission content: application/json: schema: type: object example: data: message: Permission Denied. properties: data: type: object properties: message: type: string example: Permission Denied. '422': description: Merchant does not hold funds content: application/json: schema: type: object example: data: message: >- This merchant's funds are not held; they settle automatically. properties: data: type: object properties: message: type: string example: >- This merchant's funds are not held; they settle automatically. components: securitySchemes: default: type: http scheme: bearer description: >- You can retrieve your token by visiting your dashboard and clicking Generate API token under your profile in top right. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.