lunch-money / developers Goto Github PK

The Tag Object is currently missing the archived attribute, even though I can see this attached to all tags when calling hte API for all my tags. https://lunchmoney.dev/#tags-object

The Budget object https://lunchmoney.dev/#budget-object references a config object but this object is never listed in the documentation aside from being shown in an example.

The example for Get All Assets includes a status attribute that no longer exists and is missing the exclude_transactions attribute.

https://lunchmoney.dev/#get-all-assets

It's unclear if there is a limit in the number of transactions I can push: https://lunchmoney.dev/#insert-transactions

It would be nice if the various Object documentations had a column listing which attributes are nullable. Some of them currently say so in their description, but some do not.

The Budget object can always returns an order and archived field and sometimes returns a recurring field. All of which are currently undocumented.

Example recurring field object returned

"recurring": {
  "list": [
    {"payee": "Apple", "amount": "38.3600", "currency": "cad", "to_base": 38.36},
    {"payee": "Weebly", "amount": "25.0000", "currency": "cad", "to_base": 25}
  ]
}

It is a small thing but we should rename the default branch from master to main. More and more repos are doing this and main is now the default when you create a new repo. Github has made the renaming process very easy as well https://github.com/github/renaming#rename-existing

The Transaction object https://lunchmoney.dev/#transaction-object is missing the recurring_id attribute

https://github.com/lunch-money/developers/blob/master/source/includes/_user.md#user-object

The fields on the user object don't match the JSON response (i.e. the field is called "user_id" instead of "id")

Get User

Use this endpoint to get details on the current user.

{
  "user_name": "User 1",
  "user_email": "[email protected]",
  "user_id": 18328,
  "account_id": 18221,
  "budget_name": "🏠 Family budget"
}

It's unclear exactly what the external ID does. Is it just transaction metadata? It seems to protect against duplicates. However, if you delete transaction(s) in LM it's not clear if you can add another transaction with the same external ID again.