backend-wunderlist

Backend API, and authorization

To-do list items have this basic format:

{
    "id": 1,
    "item": "Item name",
    "description": "Details or description of to-do list item",
    "due_date": "2019-05-20"
}

• id is auto-generated by 'todo' table.
• user_id is generated by our CRUD functions
• item is a string limited to 128 characters
• description is of type 'text'
• due_date is of type 'date'

https://backend-wunderlist.herokuapp.com/api/auth/register

• Required: username and password fields.

https://backend-wunderlist.herokuapp.com/api/auth/login

• Required: username and password fields.

https://backend-wunderlist.herokuapp.com/api/todos

• GET request to this route will return list of all todos per user.

• POST request to this route will add a new to-do item to logged-in user's list.

• Required field: 'item'.

• Recommended fields: 'description', 'priority', 'due_date'.

https://backend-wunderlist.herokuapp.com/api/todos/id

• GET request to this route (with 'id' replaced by todo ID) will return the todo list item with the specified ID only if associated with logged-in user.

• PUT request to this route (with valid todo ID) will update to-do item, and return number of updated items for logged-in user.

• Required field: 'item'.

• Recommended fields: 'description', 'priority', 'due_date'.

• DELETE request to this route (with valid todo ID) will delete to-do item from list, and return the number of items deleted for the logged-in user.