Notification POST only works with `/users/xyz/inbox`
If you send a notification with full serialization (i.e. you are applying filtering to the model - #39 ) without passing an inbox - i.e. to endpoint /notifications/
If doing this you'll be passing user
as a key in the request body (or the request is invalid), but you'll receive a 404
. I wrote the code without supporting this use case for budgetary reasons, in our current use cases we're only using the nested method, and resolving the foreign key from the request body has complex edge cases