Awesome

Budget Blocks DS API

Web Front-end

DS API

Video Overview

Contributers

The entirety of this repository was built in a collaborative effort between the contributors using VS Code's LiveShare extension.

Future web team members: If you have any problems with our API or have any questions, you can contact either of us via Slack or LinkedIn and we will help troubleshoot/answer any questions.

Local Setup

• Clone this repo and cd into the directory
• pipenv install to create the pip enviroment
• pipenv shell to enter the pip enviroment
• uvicorn main:app --reload to run the server locally

Tech Stack

Languages: Python, SQL, HTML

Framework: FastAPI

Deployment: AWS Elastic Beanstalk

Database: PostgreSQL hosted with ElephantSQL

• ElephantSQL login information can be found in the PVD

API Documentation

The API documentation can be found in the deployed version of the API here

Communicating with the API

/transactions

• The transaction object comes from the get request from the PLAID API (dealt on the web side).

  • Specifically, the "transactions" key from the transaction object from the PLAID API

• Specifying the user_id key tells the API to use that user's categorical preferences.

  • If a user_id doesn't exist in the database, the API creates the user in the users table and gives that user the default budget blocks categories.

• Example response:

{
  "transactions": [
    {
      "account_id": "k9VvjL1Eq3Cnk8gaQXDXt3aRVe7DaGiWekXgz",
      "account_owner": 0,
      "amount": 25,
      "authorized_date": 0,
      "category_id": "16001000",
      "date": "2020-05-15",
      "iso_currency_code": "USD",
      "location": {
        "address": 0,
        "city": 0,
        "country": 0,
        "lat": 0,
        "lon": 0,
        "postal_code": 0,
        "region": 0,
        "store_number": 0
      },
      "name": "CREDIT CARD 3333 PAYMENT *//",
      "payment_channel": "other",
      "payment_meta": {
        "by_order_of": 0,
        "payee": 0,
        "payer": 0,
        "payment_method": 0,
        "payment_processor": 0,
        "ppd_id": 0,
        "reason": 0,
        "reference_number": 0
      },
      "pending": false,
      "pending_transaction_id": 0,
      "transaction_code": 0,
      "transaction_id": "47E1jBQLoNhA6ajvnLeLCX4NwvKQmnFd7wQ8K",
      "transaction_type": "special",
      "unofficial_currency_code": 0,
      "plaid_category": [
        "Payment",
        "Credit Card"
      ],
      "budget_blocks_category": [
        "Debt"
      ]
    }
  ],
  "user_id": 1,
  "totals": {
    "Personal": 0,
    "Food": 0,
    "Debt": 25,
    "Income": 0,
    "Giving": 0,
    "Housing": 0,
    "Transportation": 0,
    "Transfer": 0,
    "Savings": 0
  },
  "request time in seconds": 0.777806282043457
}

/census

• Web team will grab the location from the user's account on Budget Blocks and pass the location parameters to the location key.

  • The parameters must have a city and state (abbreviation or full name), zipcode does not work with the API.

• Specifying the user_id tells the API to use the users categorical preferences to categorize the census data to their preferences.

• Example response:

{
  "City": "New York",
  "Personal": 2304.0833333333335,
  "Food": 725.5,
  "Debt": 0,
  "Income": 8409.25,
  "Giving": 125.66666666666667,
  "Housing": 1950.5833333333335,
  "Transportation": 707.75,
  "Transfer": 0,
  "Savings": 2595.666666666666
}

/update_users

• Plaid_cats is needed so the API knows which PLAID category it's going to be moving.

• old_BB is the current location of the PLAID category which is the value of the key Plaid_cats

• new_BB is the location where that user wants to move that PLAID category to.

• Specifying the user_id will re-categorize a specific transaction for just that user.

  • When the user has changed a transaction category, that user will not get the latest updates from the master categories if they are changed

• Example response:

{
  "message": "Updated preferences successfully"
}

/reset_user

• Resets a user's categorical preferencesvia their user_id

• Can be used if the user wants the latest update from the master categories if they want to overwrite their custom categories

/delete_user

• Deletes a user from the database if that user_id exists in the database

• Deleting a user and using requests such as /reset_user and /update_users will throw an internal error since the user does not exists in the user DB.

• A user can be re-created if the transactions from the deleted user were ran through the /transaction post request again.

• If the user that was deleted had custom categories and was re-created using /transactions, the user will be given the default master categories.

/admin routes

• /admin is a route to all the admin routes to our API

  • Login information will be stored in the PVD

• /admin/reset_user and /admin/reset_master will completely wipe all changes and will set everything back to "factory defaults"

  • There is a conformation if you are accessing the /reset_master or /reset_user through the admin panel just in case you click on it by accident.

• When using /admin/edit_master the separate plaid categories are noted by the word AND in all caps.
  • Example: Bar AND Sports Bar; Sports Bar is a sub category of Bar in PLAID.