List and search transfers for a customer
Retrieve and search transfers for a specific Customer with comprehensive filtering and pagination support. Supports searching by customer details (name, email, business name), amount ranges, date ranges, transfer status, and correlation IDs for enhanced transaction discovery. Returns paginated transfer results including status, amounts, metadata, and links to source and destination funding sources. Use this endpoint for transaction history analysis and reconciliation purposes.
Path parameters
Customer's unique identifier
Query parameters
A string to search on fields firstName, lastName, email, businessName
Only include transactions with an amount equal to or greater than startAmount
Only include transactions with an amount equal to or less than endAmount
Only include transactions created after this date. ISO-8601 format YYYY-MM-DD
Only include transactions created before this date. ISO-8601 format YYYY-MM-DD
Filter on transaction status. Possible values are pending, processed, failed, or cancelled
A string value to search on if correlationId was specified for a transaction
Number of search results to return. Defaults to 25
Number of search results to skip. Use for pagination
Headers
The media type of the response. Must be application/vnd.dwolla.v1.hal+json
Response
successful operation
Changes
Changed in 5 of the 34 revisions of this API.1221
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
- ●
added the new
fed-nowenum value to the////response property for the response statusresponse-property-enum-value-added
- ●
added the new
real-time-paymentsenum value to the////response property for the response statusresponse-property-enum-value-added
- ●
- ○
added the optional property
///to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
added the optional property
/////to the response with the statusresponse-optional-property-added
- ○
- ○
the response property
became required for the statusresponse-property-became-required
- ○
the response property
became required for the statusresponse-property-became-required
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ▲
added the new required
headerrequest parameterAcceptnew-required-request-parameter
- ▲