Amatino API v0.0.17 Released

Hot on the heels of 0.0.16, 0.0.17 delivers two changes:

  • Fixed a bug that caused Account create/update requests to fail if they contained a colour value formed as per documentation
  • Account creation/update requests will now fail with informative error messages, such as “description too long, max value 1024”, rather than a generic “400 – Bad Request”


Amatino API v0.0.16 Released

HTTP API update! 0.0.16 is now out in the wild, serving requests. Here’s what it includes:

  • Fixed a bug causing unauthorised and unauthenticated requests to return 500 errors rather than 401 / 403
  • Server header now includes the API version number
  • Fixed a bug causing Region listing to fail in certain unusual circumstances
  • Fixed a bug causing Entity permission records to enter an invalid state when that Entity was updated with a null record
  • Fixed a bug causing arbitrary requests to 500, due to a fault in Amatino’s billing system
  • Added various tests to catch aforementioned failure cases in future

Enjoy! And please continue to report bugs: @AmatinoAPI on Twitter /

Amatino API v0.0.14 Released

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 Balance and 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 Balance and RecursiveBalance objects.

Amatino API v0.0.13 released

Requests at 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.

  • EntityList page_number key has been renamed page for consistency with the UserList object.
  • EntityList has a new property, state, which is one of either "active", "deleted", or "all".

The Amatino API documentation has been updated to reflect these changes.

Amatino API v0.0.12 Now Live

Amatino API 0.0.12 is now live and serving requests at 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.

Amatino API v0.0.10 Now Live

A new version of the Amatino API is now serving requests at 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.

Amatino Web 0.0.2 Released

A new version of the Amatino Web application is now live at 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’


Amatino API v0.0.9 now live

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.