I agree for those kinds of APIs. In this case though, there is only one resource: next event and it's either present or temporarily missing. (And there's only ever R from CRUD.)
I'm having a hard time of mapping this idea into restful CRUD model. 404 kind of tells the user "you are looking from a wrong place" which is the opposite of what the domain logic here is.