# RESTfully dealing with a non-RESTful client

**URL:** <https://www.ruby-forum.com/t/restfully-dealing-with-a-non-restful-client/164682>\
**Category:** Rails\
**Created:** [April 3, 2009, 11:13pm UTC](https://www.ruby-forum.com/t/restfully-dealing-with-a-non-restful-client/164682 "2009-04-03T23:13:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jimmyether](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/e9a140/32.png) [@jimmyether](https://www.ruby-forum.com/u/jimmyether)\
**Post date:** [April 3, 2009, 11:13pm UTC](https://www.ruby-forum.com/t/restfully-dealing-with-a-non-restful-client/164682/1 "2009-04-03T23:13:30Z")

</div>

I’m working with a PBX that, given a URL string with some pre-defined  
fields, will invoke that URL with the fields filled in with collected  
data  
on certain call events.

For instance, if you give it the proper string to invoke for each new  
call,  
then when “Joe Bob” at “123-456-7890” calls, it will do an HTTP GET  
request  
on

[http://example.com/new\_call?cid\_number=1234567890&cid\_name=Joe%20Bob](http://example.com/new_call?cid_number=1234567890&cid_name=Joe%20Bob)

Easy enough to deal with, but I was wondering: if the device will only  
do  
GETs (with the params in the URI), then what’s the right way to create  
new  
Call records RESTfully, since GETs aren’t really supposed to create new  
records? Is there one?

It’s mostly curiosity. I have it working, but it’s not RESTful at all.  
🙂