logo

Income Transactions

Income Transactions
While the /incomes endpoint provides high level information about an income profile, the /income_transactions endpoint provides deeper insights into the raw data that is used to evaluate income. The /income_transactions endpoint is meant to be used in conjunction with the /incomes endpoint. After you’ve seen the summary and overview via the /incomes endpoint, the /income_transactions endpoint provides the raw transactions so you can understand the inputs into an income evaluation.
Getting Income Transactions
Like /incomes, /income_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}/income_transactions. If you’d like to see the user’s transactions, make a GET call to https://api.quovo.com/v3/users/{user_id}/income_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, income transactions for the last 12 months will be returned by default.
<span data-mce-type="bookmark" style="display: inline-block; width: 0px; overflow: hidden; line-height: 0;" class="mce_SELRES_end"></span>curl -X GET \
    -H "Authorization: Bearer a724809d37d0a21b7e9257f45cee416f5aec61993ab4b09e" \
    "https://api.quovo.com/v3/accounts/1760061/income_transactions?start_date=2016-01-01&amp;amp;amp;amp;amp;end_date=2017-01-01"
And here is a sample response:
"income_transactions": [
        {
            "account_id": 9237797,
            "connection_id": 4566463,
            "currency": null,
            "date": "2018-01-01",
            "frequency": "irregular",
            "is_payroll_agency": false,
            "id": 162835063,
            "memo": "Quovo payroll 5619641014",
            "payer": "Quovo",
            "payee": null,
            "stream_id": 0,3
            "user_id": 3238719,
            "value": 1543.3
        },
        {
            "account_id": 9237798,
            "connection_id": 4566463,
            "currency": null,
            "date": "2018-01-01",
            "frequency": "irregular",
            "is_payroll_agency": false,
            "id": 1628350396
            "memo": "Quovo payroll 5048915152",
            "payer": "Quovo",
            "payee": null,
            "stream_id": 0,
            "user_id": 3238719,
            "value": 1071.5,
        },
        {
            "account_id": 9237799,
            "connection_id": 4566463,
            "currency": null,
            "date": "2018-01-01",
            "frequency": "irregular",
            "is_payroll_agency": false,
            "id": 1628351336
            "memo": "Quovo payroll 7403422597",
            "payer": "Quovo",
            "payee": null,
            "stream_id": 0,
            "user_id": 3238719,
            "value": 5412.8,
        }
    ]
}
The response fields are separated by transaction. Each transaction has an associated   stream_id   which helps you identify the stream to which each transaction belongs. You can cross reference these transactions with the streams returned in the /incomes endpoint to get a full picture of income evaluation logic.
The response payload will also include fields that show up in the /incomes endpoint. These include the    payer  ,   payee  ,   is_payroll_agency  ,   memo  , and   frequency  .
Much like the transactions object in the /incomes 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.