I'm the developer of Firefly III and in this newsletter I talk about the technology of Firefly III and upcoming (API) so software developers know what the future will bring.
Firefly III (API) update for March 2026
|
Hi everybody! I hope this is "low volume" enough for everybody out there. I just wanted to share some small updates with you, and get your feedback on an idea I have. finishBatch API endpointNew in the API docs is the finishBatch endpoint. It is designed for users with lots of rules and webhooks, and when you enable batch processing in your /settings (this will apply to ALL users) newly submitted transactions that submit "batch_submission": false will not yet be processed untill some transaction sends "true" OR when you hit this endpoint with a POST. That way, the import itself should be faster and only the final transaction will be slower. The batch_submission field is not yet documented though, my apologies. Search deleted identifiersYou may have noticed that if you import a CSV file twice, Firefly III may refuse to import it again, even when you delete the transaction. This has always been a source of great confusion for users, until they realize how useful this is. This check however, does not work with identifier-based imports, because the search does not find these deleted transactions. A small technical detail, but an important one. Starting with v6.5.2, Firefly III will have a (documented!) endpoint where you can search for specific notes, descriptions, external identifiers or internal ids even when they are deleted. No results will be returned, just a count. The data importer can use this count to prevent duplicate transactions. Type versus typesA lot of endpoints accept the "type" field for account types, transaction types etc. The list endpoints (i.e. the transactions belonging to an account) also accept these. I found them to be a little inconsistent. Know that in the future, all endpoints will support both "type" and "types", which is expected to be a (comma separated) list of types. So either the short form (withdrawal,deposit,asset) or the long form (Asset account) will work depending on the context. As always, make sure you find me when you have questions or comments. I can address everybody on this list (over a 100 subscribers!) if necessary to clear up any questions you may have. Until the next one! Cheers, |
Firefly III
I'm the developer of Firefly III and in this newsletter I talk about the technology of Firefly III and upcoming (API) so software developers know what the future will bring.
Hello everybody! I bet you didn't expect to hear from me so soon. Tough luck! I just want to share a small API update with you that will be part of the next release. That release should go out this weekend. Changes In Firefly III v6.7.8 you can expect the following to be different. You can give categories a color, like FF0000 (no #). Firefly III doesn't use this, but it may be useful in your app and now supported natively. If you're interested, I will expand this to other objects. There is a...
Hello everybody! Long time no talk. This mailing list has been pretty low-volume and rightly so. I wouldn't want to spam all of you with weird nonsense. But now there's a small update on the new release and the API changes it will bring. TL;DR: not many changes. The new Firefly III v6.7.0 will probably be released early next week. First, here is a diff file you can check out. It lists all the changes, but since some fields are dynamic, it can be noisy. The most important changes are: You can...
Hello everybody, Thanks again for signing up! Today I want to share a few upcoming changes that will change how you interact with Firefly III, and transactions. The changes are small but could be significant. New settings New system wide settings will replace environment variables. This includes the ability to download exchange rates, and some others. This will help people who have a hard time with environment variables or simply don't want to restart Firefly III for these changes to go into...