List transfers
Return transfers across every supported payment rail, newest first. Use type to select one rail.
Authorizations
User API key authentication. Create a key under Settings → API keys in the Slash dashboard (https://app.slash.com/global-settings/api-keys) and send the x-legal-entity header naming the legal entity to act on with every request. Keys scoped to a legal entity are rejected with 403 user_api_key_required.
Headers
The legal entity to act on. Required on every request; a user API key can act on any legal entity its user has access to.
^le_[a-zA-Z0-9]+$Query Parameters
The opaque metadata.nextCursor value from the previous page. It carries that page's filters, page size and ordering, so pass it on its own; see Pagination.
Number of items per page, from 1 to 100. The page size is carried inside metadata.nextCursor, so later pages keep the same size unless limit is passed again to change it.
1 <= x <= 100Return transfers using one payment rail. Payment rail of a transfer.
ach, wire, international_wire, realtime, book Return transfers in one lifecycle state. When type is supplied, the status must apply to that rail.
Lifecycle state across every transfer rail.
pending, pending_destination, pending_approval, in_review, scheduled, canceled, failed, settled, returned Return transfers for one accessible Account.
Return transfers from one accessible virtual account.
Return transfers sent to one saved destination.
Inclusive RFC 3339 lower bound on transfer date: the date of the transfer's source transaction, which is also the list order.
Inclusive RFC 3339 upper bound on transfer date: the date of the transfer's source transaction, which is also the list order.
Response
A page of transfers.
An ACH transfer or a queued ACH awaiting destination details.
- TransferAch
- TransferWire
- TransferInternationalWire
- TransferRealtime
- TransferBook