Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Transaction JSON definitions

Michael Shadle edited this page Jan 26, 2016 · 1 revision

An attempt to define the different attributes returned

  • id (int) internal mint.com transaction ID - primary key
  • fi (string) - financial institution name
  • account (string) - account name
  • odate (text-based date format, see note) - original date
  • date (text-based date format, see note) - assume this is the edited/corrected date (if edited)
  • note (string / blob) - user supplied description/notes
  • amount (currency)
  • omerchant (string) - original merchant description
  • mmerchant (string) - "modified" merchant description? not sure.
  • merchant (string) - final merchant description - what is displayed in the UI
  • category (string) - user chosen category
  • mcategory (string) - "modified" category?
  • labels (array) - labels as (string) name and (int) id
  • isDebit (bool) - whether or not the transaction was an expense (true) or income (false)
  • isEdited (bool) - assuming this flags if the transaction has been altered from the user
  • isPending (bool)
  • isPercent (bool)
  • isMatched (bool)
  • isFirstDate (bool)
  • isDuplicate (bool)
  • hasAttachments
  • isChild (bool)
  • isSpending (bool)
  • isTransfer (bool)
  • isAfterFiCreationTime (bool)
  • manualType (int)
  • txnType (int)
  • isCheck (bool)
  • ruleMerchant
  • ruleCategory
  • ruleCategoryId (int)
  • numberMatchedByRule
  • categoryId (int)
  • userCategoryId
  • isLinkedToRule (bool)

Note on the "text-based date format" - for anything within the last month or so, it says "Jan 15" for January 15th. Once it gets older, it will show MM/DD/YY. PHP can fix it easily with date('Y-m-d', strtotime(string))

Clone this wiki locally