restful-url

i have a Rest ful service,.. and i am getting a JSON data like,.. { "returnCode": "success", "RecievedData": { "results": [ { "details": [ { "moredetails": [{ "id": "123456", "price": "129.99", "recorded_at": 3223322, "lastrecorded_at": 0002020, "seller": "google", "availability": "Available", "currency": "USD" }], "offers_count": 1, "name": "google.com", "recentoffers_count": 1, "sid": "988008555566649", "url": "http://google.com" }, "moredetails"{ . . } ] details { { [ ] } "model": "abc", "weight": "127", "price_currency": "USD", "features": { . ' } "model": "abc", "weight": "127", "price

I am developing some basic restful web services using PHP and apache and I am wondering whether I should build the URLs providing the parent entity name or not. Let me explain this better: I have 2 entities, lets suppose countries and cities . I am now just providing WS to get, create, update or delete cities but the API won't support countries manipulation via WS. I am remapping urls using mod_rewrite and I am providing the following urls in the api to manipulate cities: . GET /api/countries/<country_id>/cities cities of country with id <country_id> . GET /api/countries/<country_id>/cities/

I have already signed up for Google API Console and set up the account and API key, but my question is how do I retrieve the results from Google QPX. What causes the error below? Setting up the json Query for Google Request var FlightRequest = { "request": { "slice": [ { "origin": "DCA", "destination": "LAX", "date": "2015-02-11" } ], "passengers": { "adultCount": 1, "infantInLapCount": 0, "infantInSeatCount": 0, "childCount": 0, "seniorCount": 0 }, "solutions": 20, "refundable": false } } Requesting the Data and Returning it. $.ajax({ url: "https://www.googleapis.com/qpxExpress/v1/trips

After creating a resource controller PhotosController for a website that also does AJAX calls to the API, it appears that the resource controller can be used on both the normal website and as the API. This displays a HTML page for Photo with id = 1 http://domain.com/photos/1 and Javascript uses the following which updates the Photo resource and returns a JSON response PUT http://domain.com/api/v1/photos/1 Question: Will we have 2 PhotoControllers , one to handle API usage and one for non-API? No. You can have two separate routes point to the same controller and action. Route::get('/photos/1',

I read a lot of Restful tutorials for PHP. (I don't want to go in depth into why I am not using RoR. It is due to the team being more familiar with PHP) Because we are planning for future expansion into having APIs i read that it is important to implement Restful web services. I have looked at tutorials such as http://www.gen-x-design.com/archives/create-a-rest-api-with-php/ Apparently restful is meant for webservices. What about for webpages? can they be RESTFUL as well? if the answer is NO, please do not go beyond this line AND just tell me. Thank you. i know to make the urls look like

Thinking in a RESTful way, is it correct to use POST to create in a single call a resource and its sub-resource? In my application I have the resource /notices/{notice} and sub-resource /notices/{notice}/photos/{photo} . A {photo} can't exists without a {notice} , but a {notice} doesn't have necessarily photos. Normally, I have to do first a POST to create a notice, then another POST to add a photo. Now I want to allow the creation of a notice with a photo directly attached, enabling the creation of /notices/{notice} and /notices/{notice}/photos/{photo} with a single POST request to /notices/