logo

Expense Transactions

Expense Transactions
Quovo’s /expense_transactions endpoint provides deeper insights into the raw data that is used to evaluate expenses and create expense streams. The /expense_transactions endpoint is meant to be used as a supplement to the /expenses endpoint, in order to provide the raw transactions that underlie our expense analysis.
Getting Expense Transactions
Like /expenses, /expense_transactions can be requested at either the account or user level. If you’d like to see the raw transactions for a specific account, make a GET call to https://api.quovo.com/v3/accounts/{account_id}/expense_transactions. If you’d like to see the user’s transactions, make a GET call to https://api.quovo.com/v3/users/{user_id}/expense_transactions. You can pass a   start_date   and   end_date   if you want to see the transactions for a specific range. If you don’t specify a range, expense transactions for the trailing 12 months will be returned by default.
curl -X GET \
    -H "Authorization: Bearer a724809d37d0a21b7e9257f45cee416f5aec61993ab4b09e" \
    "https://api.quovo.com/v3/accounts/1760061/expense_transactions?start_date=2016-01-01&end_date=2017-01-01"
And here is a sample response:
{
    "expense_transactions": [
        {
            "account_id": 1056003,
            "category": "Bills/Utilities",
            "connection_id": 1029277,
            "date": "2016-11-04",
            "frequency": "monthly",
            "id": 98765432,
            "memo": "COMCAST 012345 SPA WEB ID: 123ACH_DEBIT",
            "stream_id": 1,
            "user_id": 162703,
            "value": -79.96
        },
        {
            "account_id": 1056003,
            "category": "Bills/Utilities",
            "connection_id": 1029277,
            "date": "2016-12-04",
            "frequency": "monthly",
            "id": 98765432,
            "memo": "COMCAST 012345 SPA WEB ID: 123ACH_DEBIT",
            "stream_id": 1,
            "user_id": 162703,
            "value": -107.86
        },
        {
            "account_id": 1056003,
            "category": "Bills/Utilities",
            "connection_id": 1029277,
            "date": "2017-1-04",
            "frequency": "monthly",
            "id": 98765432,
            "memo": "COMCAST 012345 SPA WEB ID: 123ACH_DEBIT",
            "stream_id": 1,
            "user_id": 162703,
            "value": -86.93
        }
    ]
}
The response fields are separated by transactions. Each transaction has an associated   stream_id   that helps you identify to which stream each transaction belongs. You can cross reference these transactions with the streams returned in the /expenses endpoint to see how the stream clustering algorithm works.
The response payload will also include fields that show up in the /expenses endpoint. These include the   cashflow_category  ,   memo  , and   frequency  .
Much like the transactions object in the /expenses endpoint, the transaction   date   and   value  , and   id   are included. Along with these, other Quovo identifiers are included as well. A full list of response fields can be found here.