API design

UserService
create-user
parameters:
username
first name
last name
password
type of user (vendor, individual)
PUT request with parameters in body
Returns 200 OK on success, 400 BAD REQUEST on failure
login
parameters:
username
password
POST request with parameters in body
Returns 200 OK and JWT on success, 400 BAD REQUEST on failure
TicketService
view-tickets
Requires JWT
JWT parsed and username extracted
GET request
Returns 200 OK and list of all tickets associated with the user (if vendor, these are the uploaded tickets, otherwise for individual, these are the purchased tickets), otherwise 400 BAD REQUEST on failure
view-venues:
Optional Parameters:
name
city
state
country
postal-code
Requires JWT
GET request
Returns 200 OK and list of all venues (filtered by optional parameters if any), otherwise 400 BAD REQUEST on failure
add-venue:
Parameters:
name
street-address
city
state
country
postal-code
addl-address
Requires JWT and user to be vendor
PUT request
Returns venue id and 200 OK on success, 400 BAD REQUEST on failure
add-performer:
Parameters:
name
description
Requires JWT and user to be vendor
PUT request
Returns performer id and 200 OK on success, 400 BAD REQUEST otherwise
view-events:
Parameters:
venue-id
start_time
end_time
performer-id
Requires JWT
GET Request
Returns 200 OK and list of events with their performers and venue (filtered by optional parameters) on success, 400 BAD REQUEST otherwise
add-performer-to-event:
Parameters:
performer-id
event-id
Requires JWT and user to be vendor
PUT request
Returns 200 OK on success, 400 BAD REQUEST on failure
upload-ticket:
Parameters:
event-id
count
section
seat
price
PUT request
Requires JWT and user to be vendor
Returns ticket id and 200 OK on success, 400 BAD REQUEST on failure
sell-ticket
Parameters:
ticket-id
count
Requires JWT and user to be individual
Removes ticket from user ticket table (decreases count if count > 1) and inserts into user selling ticket table
Returns 200 OK on success, 400 BAD REQUEST on failure
buy-ticket:
Parameters:
ticket-id
count
Requires JWT and user to be individual
Ensure the user is not attempting to buy beyond the 10 ticket-per-event threshold
Interacts with 3rd party payment service (e.g. PAYPAL) to procure payment
Returns 200 OK on success , 400 BAD REQUEST on failure