add API endpoints

[CamiloGarciaLaRotta]

Add the endpoints found in the base API Leverage the Swagger API provided by Flask-RESTPlus

[CamiloGarciaLaRotta]

Base GET/POST/PUT/DELETE for City Municipality Park Tree Civic_Location addressed by 08ad96e2b76f4538d107db5d30027cbd0cd78351 and 68a7f7d134546d9a5a3156e304d9d891d1e451b1

[CamiloGarciaLaRotta]

When the final model is complete, implement the base GET/POST/PUT/DELETE for:

• [ ] Transaction
• [ ] Review
• [ ] Order
• [ ] Assessment

Interesting endpoints to be implemented:

• [x] tree species list
• [x] civic location types list
• [ ] transaction status list
• [ ] assessment status list

[CamiloGarciaLaRotta]

@ealhomsi This is the original list of endpoints. It is deprecated, it was formulated before the feedback of the TAs Feel free to add any endpoint you need to be implemented here with a brief description of expected I/O

[CamiloGarciaLaRotta]

@ealhomsi I'll begin adding the missing resources and their respective endpoints:

Resource	Related Tables	Status
assessment	assessment	DONE
city	works_for	DONE
user	user	DONE
user	login functionality	TODO
transaction	transaction	DONE
order	order	DONE
review	review	DONE

[eliashomsi]

this is it <3 we are done after doing this and implementing the frontend

[CamiloGarciaLaRotta]

@ealhomsi I am done with the endpoints for all resources For the login, is it ok if I just do the following:

Add /uid/ to the URL paths for: Use Case: POST orders (only resident can make order) Use Case: POST reviews (only urban planners can make reviews) Use Case: POST assessement (only env scientists can make assessements)

[eliashomsi]

so basically I only need to endpoints, one to create a user and one to login with an email. GET user/{email} for login POST user/ to create a new user.

[CamiloGarciaLaRotta]

closed by #13