Accounts & Transactions
Last updated
Last updated
Retrieves the list of all available bank and cash accounts
OK
Retrieves an account by its unique ID
OK
Retrieves the list of transactions in all accounts bank and cash accounts
OK
Creates a new bank or cash account. Accounts created with this endpoint are manually tracked bank accounts. To integrate your existing bank account into Nuvio, please contact with support team.
Account name
IBAN of this bank account.
3-letter currency code for the account. You can find available currencies here.
Opening Balance to start with an existing account. It should be a decimal number with 2 decimal points. eg. 1059.34
OK
Updates an existing bank or cash account.
Account name
IBAN of this bank account.
3-letter currency code for the account. You can find available currencies here.
Opening Balance to start with an existing account. It should be a decimal number with 2 decimal points. eg. 1059.34
OK
Retrieves a single transaction by its unique ID
OK
Adds a new transaction into an existing account.
32-character unique ID of the account that the transaction belongs.
Description of the transaction
Epoch timestamp for the transaction date and time. If you don't know the timestamp, you can also provice transactionDate. If both of the fields are provided, transactionTimestamp will be used.
Datetime with timezone for the transaction date and time. You can also provide transactionTimestamp. If both of the fields are provided, transactionTimestamp will be used.
Type of the transaction. If it is an incoming money, use Money In; if it is an outgoing money, use Money Out
32-character unique ID of the customer or supplier of the transaction's sender or receiver. If you don't know the ID, you can also provide mathcingEntityCode instead of this field. If both of them are provided, matchingEntityId will be used only.
User-generated custom customer or supplier code of the transaction's sender or receiver.
Amount of the transaction. It should be a positive decimal number. eg. 1059.34
OK
Updates an existing transaction.
Description of the transaction
Epoch timestamp for the transaction date and time. If you don't know the timestamp, you can also provice transactionDate. If both of the fields are provided, transactionTimestamp will be used.
Datetime with timezone for the transaction date and time. You can also provide transactionTimestamp. If both of the fields are provided, transactionTimestamp will be used.
Type of the transaction. If it is an incoming money, use Money In; if it is an outgoing money, use Money Out
32-character unique ID of the customer or supplier of the transaction's sender or receiver. If you don't know the ID, you can also provide mathcingEntityCode instead of this field. If both of them are provided, matchingEntityId will be used only.
User-generated custom customer or supplier code of the transaction's sender or receiver.
Amount of the transaction. It should be a positive decimal number. eg. 1059.34
OK