Create routing plan for API

[noleu]

Describe the paths in the REST API as close as possible, group them in entity and describe the functionality of every endpoint

[noleu]

GET /events

• returns all events
• no auth

GET /events/{id}

• returns specific event
• no auth

GET /events/user/{userId]

• returns all events for specific user
• auth (who?)

Delete /events/{id}

• deletes the event with specified Id
• auth organizer

POST /events

• creates new event
• takes event object as input
• event object should contain name, location & date, optionally a description
• auth organizer

PUT /events/{id}

• takes event object as input
• updates all fields except of Id with the given values
• auth organizer of own event (row based)

[noleu]

GET /users

• returns all user
• auth: admin

GET /users/{id}

• gets user with the corresponding id
• auth: organizer, admin

GET /users/{email}

• gets user with the corresponding e-mail
• auth: organizer, admin

POST /users

• creates new user and stores in db
• user object as input should contain, first name, last name, e-mail and hashed password
• no auth

PUT /users/{id}

• updates user object with given values except of id
• auth: admin, me/self

GET /roles

• returns all roles
• no auth

GET /roles/{id}

• get role with specific Id
• no auth

[noleu]

does event need a filter function for date? (e.g. give me all events for 31.02.2025 )

[qimolin]

does event need a filter function for date? (e.g. give me all events for 31.02.2025 )

We could add query params for filtering

[noleu]

route for responses needs to be covered or done via events update