Entries compose Transactions. An individual entry allocates some value to an Account as either one of the fundamental Sides: a debit or a credit. All together, those debits and credits will add up to zero, satisfying the fundamental double-entry accounting equality.
When consuming the Amatino API, operations involving Entries always occur as part of a Transaction request. For example, when creating a Transaction, you will specify a JSON Array of Entry objects under the entries key. You will never send or recieve an Entry object on its own to or from the Amatino API.
The Entry Object
Amatino expects the following object structure when creating and updating Entries, and will provide the same object back to you when asked to retrieve them. Note that you never directly interact with an Entry object on its own, instead they are used as part of Transactions requests.
|description||The integer identifier of the Account to which this Entry is allocated.|
|example||"Juicy dividend on a big ol' pile of diversified stocks"|
|description||A description of this Entry. If an empty string is specified, Amatino will use the parent Transaction description to describe this Entry.|
|description||Either debit or credit.|
|max value||Somewhere north of one quadrillion (Your mileage may vary at that magnitude!)|
|description||The absolute value of this Entry, denominated in the parent Transaction unit or custom unit.|