The Amatino API has been upgraded to version
0.0.14. This release is backwards compatible with
0.0.13 and includes a fix for a bug that would cause
RecursiveBalance retrieval to fail with code
500 if the request included a
balance_time parameter. The API test suite has also been updated to more thoroughly cove the
api.amatino.io are now being served by some freshly minted code – API v0.0.13. This is a baby little release that makes changes to the EntityList object.
page_number key has been renamed
page for consistency with the UserList object.
- EntityList has a new property,
state, which is one of either
The Amatino API documentation has been updated to reflect these changes.
Amatino API 0.0.12 is now live and serving requests at
api.amatino.io. 0.0.12 resolves several issues with Transaction Version Lists (TVLs). Previously, TVLs were not operating according to the specifications in Amatino’s documentation, for either request parameters or return data. They were also at risk, under some conditions, of returning stale cached data. TVLs are now properly available.
A new version of the Amatino API is live and serving requests from
api.amatino.io. 0.0.11 fixes a bug wherein several objects would be returned with timestamps that did not match the format specified in Amatino’s documentation.
A new version of the Amatino API is now serving requests at
api.amatino.io. 0.0.10 is probably backwards compatible with 0.0.9, because it only adds new features. However, you should not depend on backwards compatibility during the 0.0.X series of releases.
- Add User List object at /users/list
- Add Entity List object at /entities/list
- Add tests for new features
Details of the User List and Entity List and how to retrieve them are available in the Amatino HTTP API documentation. Some extracts:
A User List is a collection of Users for whom the retrieving User has billing responsibility, and who were created using the Amatino API.
An Entity List enumerates the Entities that may be accessed by the retreiving User.
The use of these new objects is not immediately obvious, and they are ancillary to the core double-entry accounting functionality in Amatino. An example of Entity List usage might be displaying available Entities to a user in a client application.
A new version of the Amatino Web application is now live at https://amatino.io. Amatino Web is the software the serves the Amatino website, presenting web interfaces for billing, documentation, and other ancillary systems. Changes in 0.0.2 are:
- Remove white label Users from billing user management screen
- Remove a bunch of debug console logging that was spamming consoles
- Add ability to login by hitting return/enter rather than clicking ‘login’
A new version of the Amatino API is now live around the world. 0.0.9 is substantially backwards compatible with 0.0.8, but you should not rely on backwards compatibility during the 0.0.X series of releases.
- Performance retrieval
incomes key changed to
income, as per the relevant documentation.
- Attempts to create Transactions that include Entry’s with negative amounts will now yield 400 errors, instead of 500s.
A new version of the Amatino API is live in all regions. API 0.0.8 may be substantially backward compatible with 0.0.7, however, is not tested as such and relying on backwards compatibility during these 0.0.X releases is not recommended.
- Fixed a bug which could cause a stale, cached Performance or Position to be returned after a Transaction insertion
- Fixed a bug causing Custom Unit update requests to fail, returning a 500 code.
- Account objects now feature a ‘Children’ parameter, which contains integer IDs of all direct child Accounts.
- Fixed a rare condition wherein internal telemetry recording could fail due to a unique key constraint violation, causing the API to spew 500 errors in response to any request
- Substantial code-style enhancements in the core API to ease maintainability
- Improved test coverage over rare edge cases in Account operations
A tiny update has been released for Amatino’s Node library. 0.0.14 fixes a silly bug in the inbuilt Node version enforcement script. The script is run after installation, and was supposed to stop Node versions lower than 10.4 from running Amatino JS. Instead it was stopping versions greater than 11.0 from running it!
Amatino JS 0.0.14 is available on NPM and on GitHub.
A new version of the Amatino API has been deployed to all regions. 0.0.7 fixes a single bug, wherein the Account update requests yielded a bunch of gibberish rather than the updated Account object.