Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose Payments and Savers Information #134

Open
all64bits opened this issue Mar 6, 2024 · 2 comments
Open

Expose Payments and Savers Information #134

all64bits opened this issue Mar 6, 2024 · 2 comments

Comments

@all64bits
Copy link

My wife and I have a fairly complex system of payment splits and a large number of saver accounts with auto transfers to manage how our pay is distributed and categorised. I maintain a budget for our pay and expenses etc using a CLI application, and I replicate this budget in our Up account. However the process of inputting all of this into Up is a manual one, and prone to error.

I'd love to have this information exposed in the API so that I can do some validation and error checking on how I've set things up. If I had this info I could also programmatically compare it with our budget to make sure it aligns.

@markbrown4
Copy link
Contributor

Hi, there are other issues requesting various saver / payment information.
Are there specific fields you'd like to see?

@all64bits
Copy link
Author

all64bits commented Mar 19, 2024

Thanks for getting back to us! The set of info that would be ideal for my particular use case is:

Auto transfers (for all accounts)

  • Account name
  • Amount
  • Transfer direction & transfer account name/reference
  • Frequency
  • Next transfer date
  • Pause once goal reached (true|false)

Scheduled payments (to all payees)

  • Payee
  • From account
  • Amount
  • Description
  • Scheduled (false|date)
  • Repeating (false|frequency)
  • End after (false|number of payments)

@markbrown4 markbrown4 changed the title Feature Request: Expose Payments and Savers Information Expose Payments and Savers Information Mar 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants