Hi Ralph, Mac OS X 10.9.5 with Safari 7.1.2.
The first time I clicked on the link it asked me for a certificate, which seemed pointless to give it for API docs so I clicked Cancel. Then it displayed the error. On subsequent attempts it goes straight to the error. I guess the browser must be remembering my initial response. I had been hoping to see how a RESTful web service could be easy to use, since in my experience they?ve always been at least an order of magnitude more difficult than SOAP, at least with .NET systems where basically you just enter the URL and click a few buttons and hey presto, you have a bunch of proxy classes that you can easily program against with full type-safety ? as opposed to hours or days of reading docs, which are probably inaccurate, and trial-and-error tearing your hair out with frustration to find simple typos or type errors, wondering how you?ve suddenly time-travelled back into the 1970s. But maybe there are nice technologies out there for consuming RESTful services easily that I?ve never encountered, so I was intrigued to learn. I do like your description of the API of MediRecord, even if am sceptical about its ease of use ;-) Peter On 20 Jan 2015, at 0:01, Ralph van Etten <ralph at medvision360.com> wrote: > Hi Peter, > > >> This has lead to our current version of MedRecord (which is still work in > >> progress) and can be found here: >>> >>> https://mr.dev.medvision360.org/mr/apidocs/#!/ >> >> >> Hi Ralph, >> >> That link doesn?t work. It displays this: >> >> {"error":406,"message":"The resource identified by the request is only >> capable of generating response entities which have content characteristics >> not acceptable according to the accept headers sent in the >> request","cause":"user?} > > I am sorry to hear that. > Can you tell me what browser you are using and for which platform (Windows, > OSX, Linux)? > > Thanks, > > Ralph van Etten > MedVision360
