I’m designing a REST API of service and got stuck on proper way to nest resources.

Resources: partners, tickets, settings

Connections 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 resources

GET /partners – list all partners
GET /partners/:id – show details of the partner specified by :id parameter
GET /partners/:partner_id/tickets – list of partner’s tickets
GET /partners/:partner_id/tickets/:id – details of the specified partner’s ticket
POST /partners/:partner_id/tickets – saves new ticket
PUT /partners/:partner_id/tickets/:id – updates the ticket specified by :id parameter
GET /partners/:partner_id/settings – list partner’s settings
PUT /partners/:partner_id/settings – update partner’s settings

Problem/Question

Would it be proper way to split nested resources (tickets, settings) to seperate resources or duplicate them as seperate resources?

E.g.

GET /tickets/:id
POST /tickets
PUT /tickets/:id

GET /settings
PUT /settings