Data Sources

Hurdlr's Income Streams API sits directly on top of your Plaid or MX integration. If you don't have an integration yet, Hurdlr enables you to skip past the burden of building your own back-end to store all that transaction (and related) data. Or, if you already have an integration, you can leverage Hurdlr's Income Streams API to enrich the data you're already storing.

Once you have your data source integration interfaced with the Hurdlr API (less than one calendar day of labor), you can immediately start using all of Hurdlr's Income Streams functionality.

1. Connecting your Plaid or MX integration

Please reference our Plaid integration or MX integration documentation for detailed instructions on connecting your data sources with the Hurdlr API.

2. Displaying the user's income and allowing them to make edits

You can easily allow your users to view their income transactions and make quick edits, including the ability to split across multiple revenue accounts, by rendering Hurdlr Embedded's Income Dashboard.

3. Programmatically getting the user's income

If you are building your own user experience or want to perform programmatic processing on a user's income transactions, you can retrieve those revenues from the Hurdlr API.

On each revenue, you may find the following attributes to be of particular interest:

FieldDescriptionFormat
idId of the revenue recordNumeric
typeType of revenueMust be one of the following: "PENDING", "BUSINESS", "NOT_BUSINESS"
dateDate that the revenue was depositedyyyy-MM-dd'T'HH:mm:ss.SSSZ
amountTotal value of the depositNumeric, with 2 decimal places
lastUpdatedDateLast date/time that this record was modifiedyyyy-MM-dd'T'HH:mm:ss.SSSZ

Additionally, several attributes to help you or your user identify a bank transaction are listed below:

FieldDescriptionFormat
bankDescriptionTransaction description (similar to what will show on the user's bank statement)Any string
apiInstitutionIdId of the institution that the transaction originated fromAny string
apiAccountNameDisplay name for the user's bank accountAny string
apiAccountNoMask of the user's bank account, often the last 4 digits of the account number2-4 Alphanumeric characters
plaidItemAccountIdId of the bank account that this transaction originated from (within Hurdlr's API)Numeric
apiNameName of the API that this transaction originated fromWill always be "PLAID", unless you are utilizing one of Hurdlr's other direct integrations
apiPaymentIdId of the transaction record in Plaid's APIAny string