<< GET /rest/1.0/devices/9764e31d-65bf-4b2a-a3f1-8b0cdad6e8d6
>> 200 OK
   { entry : [
     {"id": "skype:foobar", "label":"skype", "carrier":"Skype" },
     {"id": "tel:16504568790", "label":"home phone", "carrier":"ATT", "ccfCheck":"passed"},
     {"id": "xmpp:foo@bar.com", "label":"gtalk", "carrier":"Google"},
     {"id": "mailto:foo@bar.com", "label":"email", "mailCheck":"passed"}
   ] }

<< PUT /apps/mydomain:myapp/          
   { "notificationUrl" : "http://myapp.com/"}

>> 200 OK
   {"entry":[
    {"id":"mydomain:myapp","domain":"mydomain","name":"myapp",
     "createdWith":"develperportal","createdBy":"9de95885-09c7-4551-9ce6-dcd5f66f20c8",
     "created":"2009-03-31T15:38:01Z","visible":false,"suspended":false,
     "template":[  {"type":"mailto","required":true,"alias":"","verifier":"auto"},
                   {"type":"tel","required":true,"alias":"","verifier":"auto"}]

<< DELETE /rest/1.0/devices/976e31d-6bf-4b2f-a3f1-8bcda6e8d6/tel:15108768904

>> 200 OK 
   REMOVED: /rest/1.0/devices/976e31d-6bf-4b2f-a3f1-8bcda6e8d6/tel:1510876890

• Invalid request URI
• Invalid HTTP Header
• Receiving an unsupported, nonstandard parameter
• Receiving an invalid HTTP Message Body

• Missing OAuth authorization credentials as described in OAuth Consumer Request 1.0, http://oauth.googlecode.com/svn/spec/ext/consumer_request/1.0/drafts/1/spec.html
• OAuth authorization credentials are present, but the User identity is not authorized to access the protected resource. If the request already included authorization credentials, the 401 response indicates that the request has been refused for those credentials. A 401 response MUST include a WWW-Authenticate header field indicating the request, and MAY present an OAuth Token for the container server's realm. Example: WWW-Authenticate: OAuth realm="http://sp.example.com/"

• startIndex — the index of the first result returned in this response, relative to the starting index of all results that would be returned if no startIndex had been requested. In general, this will be equal to the value requested by the startIndex, or 0 if no specific startIndex was requested.
• itemsPerPage — the number of results returned per page in this response. In general, this will be equal to the count Query Parameter, but MAY be less if the Service Provider is unwilling to return as many results per page as requested, or if there are less than the requested number of results left to return when starting at the current startIndex. This field MUST be present if and only if a value for count is specified in the request.
• totalResults — the total number of items that would be returned if there were no startIndex or count specified. This value tells the Consumer how many total results to expect, regardless of the current pagination being used, but taking into account the current filtering options in the request.
• entry — an array of objects, one for each item matching the request. For consistency of parsing, if the request could possibly return multiple items, this value MUST always be an array of results, even if there happens to be 0 or 1 matching results. If the result is specifically for a single item then the entry MUST be an object containing the single item returned.

<< GET /rest/1.0/calls/<guid>?startIndex=10&count=5

>> { "startIndex" : 10,
     "itemsPerPage" : 5, 
     "totalResults" : 100,
     "entry" : [
      {...first item...},
      {...second item...}
      ...
   ]
}