You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Too much data transfer and client side filtering: AKA Zeus is unusable with 30K payments.
Describe the solution you'd like
ListPaymentsRequest has some nice filtering capability
include_incomplete
index_offset
max_payments
reversed
creation_date_start
creation_date_end
It would be nice to also be able to filter the invoice amount paid (max and/or min), as well as a memo search query. We may have many small payments over a small time period that we don't want to look at.
ListInvoiceRequest has
pending_only
index_offset
num_max_invoices
reversed
creation_date_start
creation_date_end
For invoices, it would also be nice to also be able to filter the invoice amount (max or min), as well as a memo search query. Additionally, it would be nice to be able to show paid invoices only instead of showing unpaid invoices only.
Describe alternatives you've considered
They're all slow.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Too much data transfer and client side filtering: AKA Zeus is unusable with 30K payments.
Describe the solution you'd like
ListPaymentsRequest
has some nice filtering capabilityIt would be nice to also be able to filter the invoice amount paid (max and/or min), as well as a memo search query. We may have many small payments over a small time period that we don't want to look at.
ListInvoiceRequest
hasFor invoices, it would also be nice to also be able to filter the invoice amount (max or min), as well as a memo search query. Additionally, it would be nice to be able to show paid invoices only instead of showing unpaid invoices only.
Describe alternatives you've considered
They're all slow.
The text was updated successfully, but these errors were encountered: