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

Api endpoint suggestion to match payee rule #258

Open
TheFern2 opened this issue Aug 31, 2023 · 1 comment
Open

Api endpoint suggestion to match payee rule #258

TheFern2 opened this issue Aug 31, 2023 · 1 comment

Comments

@TheFern2
Copy link

I am currently working on a side project which will fwd emails from transactions to a budget. Currently working on the ynab api, but I will plan to support actual as well. One thing where actual api is better is that it offers payee rules endpoints where as ynab doesn't. So if I want to send the correct transaction I have to implement rule matching on my end as well. For actual since most of it is already on the api, I think matching a payee string from a transaction will be pretty sweet to get a payee id. Otherwise I guess it would be up to the application to cache all payees, and then call getPayeeRules for all payees. Then a transaction will check if it matches with any rule.

getPayeeIDByRuleMatch(transactionPayeeString) → Promise<PayeeID>

Also I noticed on the api ref docs, it says api not deployed yet, is this still the case?

@Bazoogle
Copy link

Bazoogle commented Nov 18, 2023

That page is very outdated. According to an archive of the website, the API was released in October of 2019. And if you go to the Github page for the API, you can see it is in fact archived now. It seems James Long, the original founder, made his project open source and the website is stuck in this outdated limbo.

Seems to me the API documentation is here where the API is now a package inside the main github page for Actual (found here, as linked in the documentation)

This is just from my quick research also looking for the API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants