Be able to set individual read/write permissions for individual API keys e.g. write-only for transactions & read-only for categories for an app that should only add transactions

Right now the only "Synced" account is the default Plaid managed accounts. To support future third-party tools, create an object that is as close to the Plaid object while being manually managed by said third party. This should show similarly as the Plaid accounts and have the option to say what third party added it and other similar labels elsewhere.

Would be great to be able to manage rules, especially when ingesting from multiple sources.

Useful for users building out their own native apps for Lunch Money. We don't want to always be relying on a singular developer token!

It looks like new tags are created by passing a new string tag to updated or new transactions. It would be nice to be able to create tags separately instead of requiring them to be associated with a transaction at the start.

I have crypto held in multiple places, some of which are not supported by the automatic sync. It's aggregated by the index purchasing bot I built ( https://github.com/iloveitaly/crypto-index-fund-bot ) and I'd like to use that bot as my master record of crypto held. Ideally, I could write a script to sync holding amounts from that bot, but I'd need a POST https://dev.lunchmoney.app/v1/crypto to dynamically create new accounts when new currencies are purchased.

It would be helpful to have a metadata hash available on each account. For instance, if you were tracking a car value, you could stick a CarFax or Edmunds URL in the metadata of the account, which would allow a script or app to dynamically update the value.

Additional properties of created_at / updated_at would be very useful for all objects returned. These would especially be useful as query params on the /v1/transactions endpoint too.

It would be great to make the data queryable via the API.