You can access any REST API with PHPs cURL Extension. However, the API Documentation (Methods, Parameters etc.) must be provided by your Client! Example: // Method: POST, PUT, GET etc // Data: array(“param” => “value”) ==> index.php?param=value function CallAPI($method, $url, $data = false) { $curl = curl_init(); switch ($method) { case “POST”: curl_setopt($curl, CURLOPT_POST, 1); … Read more
I’ve tried both design strategies – nested and non-nested endpoints. I’ve found that: if the nested resource has a primary key and you don’t have its parent primary key, the nested structure requires you to get it, even though the system doesn’t actually require it. nested endpoints typically require redundant endpoints. In other words, you … Read more
I built one of the first SOAP servers, including code generation and WSDL generation, from the original spec as it was being developed, when I was working at Hewlett-Packard. I do NOT recommend using SOAP for anything. The acronym “SOAP” is a lie. It is not Simple, it is not Object-oriented, it defines no Access … Read more
As far as i know this issue appears only for the pathvariable at the end of the requestmapping. We were able to solve that by defining the regex addon in the requestmapping. /somepath/{variable:.+}
This worked for me: curl -v –cookie “USER_TOKEN=Yes” http://127.0.0.1:5000/ I could see the value in backend using print(request.cookies)
The ASP.NET Web API has replaced the WCF Web API previously mentioned. I thought I’d post an updated answer since most of these responses are from early 2012, and this thread is one of the top results when doing a Google search for “call restful service C#”. Current guidance from Microsoft is to use the … Read more
No, REST is the way HTTP should be used. Today we only use a tiny bit of the HTTP protocol’s methods – namely GET and POST. The REST way to do it is to use all of the protocol’s methods. For example, REST dictates the usage of DELETE to erase a document (be it a … Read more
You can expose the service in two different endpoints. the SOAP one can use the binding that support SOAP e.g. basicHttpBinding, the RESTful one can use the webHttpBinding. I assume your REST service will be in JSON, in that case, you need to configure the two endpoints with the following behaviour configuration <endpointBehaviors> <behavior name=”jsonBehavior”> … Read more
For me I usually send back an HttpResponseException and set the status code accordingly depending on the exception thrown and if the exception is fatal or not will determine whether I send back the HttpResponseException immediately. At the end of the day it’s an API sending back responses and not views, so I think it’s … Read more
If “validation failure” means that there is some client error in the request, then use HTTP 400 (Bad Request). For instance if the URI is supposed to have an ISO-8601 date and you find that it’s in the wrong format or refers to February 31st, then you would return an HTTP 400. Ditto if you … Read more