I'm designing a REST API of service and got stuck on proper way to nest resources.Resources: partners, tickets, settingsConnections between resources:partner has many tickets,partner has set of settings,Bussines logic:you can list all partners as anonymous user,you can add new ticket to specified partner as anonymous user,only partner can list his tickets,only partner can modify his tickets,only partner can list settings,only partner can modify settings,What I did till now:Partner resourcesGET /partners - list all partnersGET /partners/:id - show details of the partner specified by :id parameterGET /partners/:partner_id/tickets - list of partner's ticketsGET /partners/:partner_id/tickets/:id - details of the specified partner's ticketPOST /partners/:partner_id/tickets - saves new ticketPUT /partners/:partner_id/tickets/:id - updates the ticket specified by :id parameterGET /partners/:partner_id/settings - list partner's settingsPUT /partners/:partner_id/settings - update partner's settingsProblem/QuestionWould it be proper way to split nested resources (tickets, settings) to seperate resources or duplicate them as seperate resources?E.g.GET /tickets/:idPOST /ticketsPUT /tickets/:idGET /settingsPUT /settings
What is the proper way of nesting resources in REST model?
api;rest;api design