During the creation of the chrome extension a few issues have arisen that are worth mentioning.
The device page for individual devices are meant to display a list of the delivery PINs that are associated with the device. In the original API schema it had been somewhat assumed that the device endpoint would be able to handle this type of request. In the actual implementation however it would be putting unfitting to put such logic in the device endpoint. The device endpoint is responsible for the actual devices not what the device have registered as deliveries. However, putting this in the delivery endpoint would also make little sense. The delivery endpoint is for dealing with single delivery PINs. Thus we fall upon the same reason that the owns endpoint was built which is to represent a relationship between database tables. Therefore another endpoint called /deliveries/ was added. Where a user can specify their unique deviceName (different from the display common name) and get the delivery PINs associated.