 <p>Looking at the WSDL for the message is irrelevant because as you have said in a response to a comment you want this to be a REST based service and WSDL is a SOAP construct. On that basis you should remove a <code>&lt;serviceMetadata&gt;</code> behavior if you have one as this is about SOAP metadata. </p> <p>To diagnose problems like this you should turn on tracing in WCF (I have a short screencast <a href="http://www.rocksolidknowledge.com/Screencasts.mvc/Watch?video=WCFTracing.wmv" rel="nofollow">here</a> that shows you how to do it). This should highlight what the problem is in processing the message</p> <p>To wire up the REST plumbing without adding a section in the config for your service add the following to your config file under the system.serviceModel section</p> <pre><code>&lt;protocolMapping&gt; &lt;add scheme="http" binding="webHttpBinding"/&gt; &lt;/protocolMapping&gt; &lt;behaviors&gt; &lt;endpointBehaviors&gt; &lt;behavior&gt; &lt;webHttp/&gt; &lt;/behavior&gt; &lt;/endpointBehaviors&gt; &lt;/behaviors&gt; </code></pre>