parent
99909c439b
commit
a546daca6f
2 changed files with 59 additions and 1 deletions
@ -0,0 +1,58 @@ |
||||
--- |
||||
title: 'Expense Tracker API' |
||||
description: 'Build an API for an expense tracker application.' |
||||
isNew: false |
||||
sort: 9 |
||||
difficulty: 'beginner' |
||||
nature: 'API' |
||||
skills: |
||||
- 'Programming Language' |
||||
- 'Data modeling' |
||||
- 'User Authentication' |
||||
seo: |
||||
title: 'Expense Tracker API Project Idea' |
||||
description: 'Build an API for an expense tracker application.' |
||||
keywords: |
||||
- 'backend project idea' |
||||
roadmapIds: |
||||
- 'backend' |
||||
--- |
||||
|
||||
Build an API for an expense tracker application. This API should allow users to create, read, update, and delete expenses. Users should be able to sign up and log in to the application. Each user should have their own set of expenses. |
||||
|
||||
![Expense Tracker API](https://assets.roadmap.sh/guest/expense-tracker-api-m72p5.png) |
||||
|
||||
## Features |
||||
|
||||
Here are the features that you should implement in your Expense Tracker API: |
||||
|
||||
- Sign up as a new user. |
||||
- Generate and validate JWT tokens for handling authentication and user session. |
||||
- List and filter your past expenses. You can add the following filters: |
||||
- Past week |
||||
- Past month |
||||
- Last 3 months |
||||
- Custom (to specify a start and end date of your choosing). |
||||
- Add a new expense |
||||
- Remove existing expenses |
||||
- Update existing expenses |
||||
|
||||
## Constraints |
||||
|
||||
You can use any programming language and framework of your choice. You can use a database of your choice to store the data. You can use any ORM or database library to interact with the database. |
||||
|
||||
Here are some constraints that you should follow: |
||||
|
||||
- You’ll be using [JWT (JSON Web Token)](https://itnext.io/demystifying-jwt-a-guide-for-front-end-developers-ead6574531c3) to protect the endpoints and to identify the requester. |
||||
- For the different expense categories, you can use the following list (feel free to decide how to implement this as part of your data model): |
||||
- Groceries |
||||
- Leisure |
||||
- Electronics |
||||
- Utilities |
||||
- Clothing |
||||
- Health |
||||
- Others |
||||
|
||||
As a recommendation, you can use MongoDB or an ORM for this project, such as [Mongoose](https://mongoosejs.com/) (if you’re using JavaScript/Node for this). |
||||
|
||||
|
Loading…
Reference in new issue