The replies here make me sad. Two answers: 1) Honk is not a resource and using REST here makes no sense. When you want to send actions across network, RESTful

The replies here make me sad. Two answers: 1) Honk is not a resource and using REST here makes no sense. When you want to send actions across network, RESTful HTTP is not as good of a technology as, say, Websockets. See http://blog.arungupta.me/2014/02/rest-vs-websocket-comparison-benchmarks/ http://blog.arungupta.me/2014/02/rest-vs-websocket-compariso... 2) If you must use RESTful HTTP, this would be a GET with an Authorization header that contains an authorization token. This solves the Google spider problem and, well, the fact that you don't want just anyone honking your horn! :)