Recurring Transactions API
Recurring transactions are a beta feature. How monetr detects them and what the object looks like are both subject to significant changes, so expect this page to move around a bunch before it settles down.
Once monetr has grouped your transactions into similar transaction clusters, it looks at each cluster and tries to work out whether it happens on a schedule. Your streaming service on the 12th every month, a paycheck every other Friday, car insurance once a year. When it finds a schedule that holds up, that's a recurring transaction.
A recurring transaction only ever goes one direction. Money going out and money coming in get looked at separately, so a cluster can have at most two of them, one for the charges and one for the refunds or deposits. Most only ever have one.
monetr wants at least three transactions before it'll call something recurring, and it has to be pretty sure about the schedule. Two charges a month apart is a coincidence as far as it's concerned.
Like the clusters, this all happens in a background job. It runs right after the clusters get recalculated, so a brand new transaction won't count toward anything until both jobs have gotten to it.
Each transaction has a transactionRecurringId pointing at the recurring
transaction it's part of. That's how you'll find these for now, there's no endpoint to list them yet.
The recurring transaction object
The ruleset keeps its DTSTART in UTC like every other ruleset in monetr, but the schedule is really in your
account's timezone. If you want to pull dates out of it yourself, move DTSTART into your account's timezone first.
Skip that and something like BYMONTHDAY=8 lands on the 9th for anyone east of UTC.
ended and deleted aren't the same thing. Something that ended still exists, it just isn't happening anymore. If a
cluster stops recurring entirely, or the cluster itself goes away, the recurring transaction gets deleted. Its ID stops
working and the transactions that were in it go back to a null transactionRecurringId.
GET Get a recurring transaction
Returns one recurring transaction. You'll usually get the ID from a transaction's transactionRecurringId.
In the app: Nothing in the app calls this yet.
Auth: API key, subscription required.
Path parameters
Example
That one's a monthly charge on the 12th that went up from 15.49 partway through, which is why amounts has
two entries.