Hi I'm working with an API Where an employee can see his Vacation (overview and balance) and Request new Vacation. A manager can Approve or Reject a Request for Vacation. He can also create Vacation on behalf of an employee.I'm in doubt what would be the best design. Most understandable for a developer (say mobile developer, consuming the API)I have two main questions:1) Should I expose VacationRequest as its own resource, or just as a specific state of a Vacation resource./vacation/vacations/requests/preview (employee post to preview effect of a vacation request, employee_id is in request body,  system returns vacation summary)/vacation/vacations/requests (employee post a vacation request, employee_id is in request body, system returns vacation summary)/vacation/vacations/preview (employee post to preview effect of new vacation with state= requested. etc.)/vacation/vacations (manager post vacation on behalf of employee)/vacation/vacations/{vacation_id}/approval  (manager post approval of vacation for employee)2) should I only have uri template like /vacation/vacations/{vacation_id}or would it be better to split into/vacation/vacations/{vacation_id}  (used by manager)/vacation/employees/{employee_id}/vacations/{vacation_id} (used by employee)
REST Resource design
rest;api design;resources;uri