Adding future transactions

Hi,

I'm working on automatic import from my credit card, and I would like to add future transactions for payments. In Israel the future payments are known, and I would like to have the future transactions so I will be able to budget for them.

I tried to just use the regular transaction POST, but I get a "date must not be in the future or over 5 years ago" error. Is it possible to add a future transaction using the API? I really expected to be able to see my future credit card payments in YNAB.

Thanks,

Noam

9replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • I don't think it's currently possible, since the `/budgets/{budget_id}/scheduled_transactions` endpoint is read-only (doesn't support POST method).  Would be a nice feature.

    Reply Like
  • Correct, scheduled transactions aren't currently possible, but it's on the list. Similar discussion here.

    Reply Like
  • I should have mentioned:  I've noted your interest Noam Yorav-Raphael  🙂

    Reply Like
    • George I agree. I really would like to see all API endpoint include create and update access, but this especially since we already have such access for real-time transactions. Any news on this or more generally more write access via the API? Is it at least something that is planned?

      I too was hoping to be able to do this to automate recording of PIF card payments each month. The card is already setup with the bank to pull the statement balance each month from my checking, I was wanting to on the statement close date each month have a script grab the current balance of the card and enter a one time scheduled transaction for that amount on the due date.

      Reply Like
  • Hey George — I’d also like to cast my vote for this ☺️

    Reply Like
    • Ben Khaki Storm
    • YNAB book topics online: https://support.youneedabudget.com/r/q5w48j
    • Khaki_Storm.1
    • 3 wk ago
    • Reported - view

    You can manually enter a future transaction with reoccurrence, correct? You'd only have to do it once. 

    Reply Like
      • nolesrule
      • YNAB4 Evangelist
      • nolesrule
      • 3 wk ago
      • Reported - view

      Ben Khaki Storm This is regarding API usage.

      Reply Like
      • Ben Khaki Storm
      • YNAB book topics online: https://support.youneedabudget.com/r/q5w48j
      • Khaki_Storm.1
      • 3 wk ago
      • Reported - view

      nolesrule I understood that. However, a one time manual entry might help. Just an idea, YMMV. I sit on the fence at work between the developers and end users. We had a conversation like this at my work this week: there's a complex data setup that involves a lot of business rules and some just come down to human experience, but once the data is entered (really building relationships between data objects), the API to keep each individual data object up to date is straight forward. I thought a similar approach might help here. 

      Reply Like
  • Slate Blue Sander and Stephan Seidt If you have a moment, would you mind submitting a Feature Request for this? That lets our development team know what's important to you. Thanks!

    And anyone else interested can do the same. :)

    Reply Like
Like1 Follow
  • 1 Likes
  • 2 wk agoLast active
  • 9Replies
  • 195Views
  • 8 Following