> ## Documentation Index > Fetch the complete documentation index at: https://docs.fintoc.com/llms.txt > Use this file to discover all available pages before exploring further. # List transfer batches > Lists the transfer batches of your organization in the `live` or `test` mode of the API key used, including the batches created from the Dashboard. Filter by `status`, or by creation date range with `since` and `until`. The list is paginated. Use the `starting_after`, `ending_before`, and `limit` query parameters to page through it. The `Link` response header carries the URLs to navigate the pages. To read the transfers of a batch, call `GET /v2/transfers` with the `transfer_batch_id` query parameter. ## OpenAPI ````yaml reference/core-api.json GET /v2/transfer_batches openapi: 3.1.0 info: title: Fintoc API version: v2026-02-01 servers: - url: https://api.fintoc.com security: [] paths: /v2/transfer_batches: get: tags: - Transfer batches summary: List transfer batches description: >- Lists the transfer batches of your organization in the `live` or `test` mode of the API key used, including the batches created from the Dashboard. Filter by `status`, or by creation date range with `since` and `until`. The list is paginated. Use the `starting_after`, `ending_before`, and `limit` query parameters to page through it. The `Link` response header carries the URLs to navigate the pages. To read the transfers of a batch, call `GET /v2/transfers` with the `transfer_batch_id` query parameter. operationId: transfer-batches-list parameters: - name: status in: query required: false schema: type: array items: type: string enum: - pending_authorization - rejected - expired - in_progress - succeeded - partially_succeeded - failed description: >- Statuses to filter by. One or more of `pending_authorization`, `rejected`, `expired`, `in_progress`, `succeeded`, `partially_succeeded`, and `failed`. Returns the batches whose `status` matches any of the values you provide. - name: since in: query required: false schema: type: string format: date-time example: '2026-01-01T00:00:00Z' description: >- Lower bound for the creation date. Returns batches created on or after this ISO 8601 datetime in UTC. - name: until in: query required: false schema: type: string format: date-time example: '2026-03-31T23:59:59Z' description: >- Upper bound for the creation date. Returns batches created on or before this ISO 8601 datetime in UTC. - name: starting_after in: query required: false schema: type: string example: trbatch_2rNxBkOrlHoOYsZTyQYhA0o8Ek0 description: >- Cursor that fetches the next page of batches. Use the ID of the last batch from the current page. - name: ending_before in: query required: false schema: type: string example: trbatch_2rNxBkOrlHoOYsZTyQYhA0o8Ek0 description: >- Cursor that fetches the previous page of batches. Use the ID of the first batch from the current page. - name: limit in: query required: false schema: type: integer example: 50 description: >- Maximum number of batches to return per page. Ranges from `1` to `300`. Defaults to `30`. responses: '200': description: List of transfer batches for the current mode. headers: Link: schema: type: string description: URLs to navigate the paginated list, as defined by RFC 8288. content: application/json: schema: type: array items: $ref: '#/components/schemas/transfer_batch' '400': description: 'Invalid request: a query parameter is invalid.' content: application/json: examples: invalid_enum: value: error: code: invalid_enum message: >- Invalid status: ["authorized"]. Must be one of 'pending_authorization', 'rejected', 'expired', 'in_progress', 'succeeded', 'partially_succeeded' or 'failed'. invalid_params: value: error: code: invalid_params message: >- Cannot use starting_after and ending_before params at the same time schema: $ref: '#/components/schemas/error_object' '401': description: Invalid or missing API key. content: application/json: examples: invalid_api_key: value: error: type: authentication_error code: invalid_api_key message: 'Invalid API Key: invalid-*oken' schema: $ref: '#/components/schemas/error_object' '501': description: Transfer batches are not available for your organization. content: application/json: examples: operation_not_implemented: value: error: code: operation_not_implemented message: Operation not implemented for this region schema: $ref: '#/components/schemas/error_object' security: - api_key: [] components: schemas: transfer_batch: type: object description: >- A group of outbound transfers that you create in one request and approve once from the Dashboard. Fintoc sends the transfers in the batch after you approve the batch. List them with `GET /v2/transfers` and the `transfer_batch_id` query parameter. properties: id: type: string description: Unique identifier of the transfer batch. example: trbatch_2daFu0zqqDtZGJaSi2TGI2Mm1nN object: const: transfer_batch description: Type of the object. Always `transfer_batch`. amount: type: integer description: >- Sum of the amounts of the transfers in the batch, in the smallest currency unit. For MXN this is centavos; CLP has no minor unit. example: 150000 authorized_at: type: - string - 'null' format: date-time description: >- Time the batch was approved from the Dashboard, as an ISO 8601 datetime in UTC, or `null`. example: '2026-03-01T12:05:00Z' created_at: type: string format: date-time description: Time the batch was created, as an ISO 8601 datetime in UTC. example: '2026-03-01T12:00:00Z' currency: type: string enum: - CLP - MXN description: Currency of the transfers in the batch. One of `CLP`, `MXN`. example: MXN description: type: string description: Human-readable label for the batch. Up to 40 characters. example: Supplier payouts March expired_at: type: - string - 'null' format: date-time description: >- Time the batch expired without approval, as an ISO 8601 datetime in UTC, or `null`. example: null mode: type: string enum: - live - test description: Whether the batch is `live` or `test` data. example: test partially_succeeded_at: type: - string - 'null' format: date-time description: >- Time the batch finished after only some transfers succeeded, as an ISO 8601 datetime in UTC, or `null`. example: null rejected_at: type: - string - 'null' format: date-time description: >- Time the batch was rejected from the Dashboard, as an ISO 8601 datetime in UTC, or `null`. example: null settled_amount: type: integer description: >- Sum of the `settled_amount` of the transfers in the batch, in the smallest currency unit. For MXN this is centavos; CLP has no minor unit. example: 0 status: type: string enum: - pending_authorization - rejected - expired - in_progress - succeeded - partially_succeeded - failed description: >- Lifecycle status of the batch. One of `pending_authorization` (waiting for approval in the Dashboard), `rejected` (rejected in the Dashboard), `expired` (not approved in time), `in_progress` (approved, with transfers being sent), `succeeded` (every transfer succeeded), `partially_succeeded` (some transfers succeeded), or `failed` (no transfer succeeded). example: in_progress succeeded_at: type: - string - 'null' format: date-time description: >- Time every transfer of the batch succeeded, as an ISO 8601 datetime in UTC, or `null`. example: null succeeded_count: type: integer description: Number of transfers in the batch that succeeded. example: 0 transfer_count: type: integer description: Number of transfers in the batch. example: 3 required: - id - object - amount - authorized_at - created_at - currency - description - expired_at - mode - partially_succeeded_at - rejected_at - settled_amount - status - succeeded_at - succeeded_count - transfer_count error_object: type: object properties: error: type: object description: Details of the error that caused the request to fail. properties: code: type: string description: >- Machine-readable code identifying the specific error, for example `invalid_request`. example: invalid_request doc_url: type: string description: >- URL of a documentation page with more details about the error. Not returned by every error. example: https://docs.fintoc.com/reference/errors message: type: string description: Human-readable message describing the error. example: 'Missing required param: account_id' param: type: - string - 'null' description: >- Name of the request parameter that caused the error. Not returned by every error. example: account_id type: type: string description: >- Category of the error, for example `invalid_request_error` or `authentication_error`. Not returned by every error. example: invalid_request_error required: - code - message required: - error securitySchemes: api_key: type: apiKey name: Authorization in: header ````