function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
David BrinkDavid Brink 

"Security requirements are not satisfied because the security header is not present in the incoming message" error

I am trying to figure out how to work with the Marketing Cloud API and am not having much luck (documentation here:  The web service URL I used was  Here is my code (mostly copied from the "starter kit" example code):
            m_Client.ClientCredentials.UserName.UserName = "";
            m_Client.ClientCredentials.UserName.Password = "passw0rd";

            //Local variables
            APIObject[] Results;
            String requestID;
            String status;

            // Instantiate the retrieve request
            RetrieveRequest rr = new RetrieveRequest();
            rr.ObjectType = "DataExtensionObject[810f461c-231a-440a-8543-837460be6c7a]";//required

            rr.Properties = new string[] { "subscriber_key" };//required //Any Column on the Data Extension
            string a = rr.ToString();
            status = m_Client.Retrieve(rr, out requestID, out Results);
This code errors on the last line (error detail in the SOAP response below).
The "Retrieve" function in the last line sends this SOAP request:
<s:Envelope xmlns:s="">
 <s:Body xmlns:xsi="" xmlns:xsd="">
  <RetrieveRequestMsg xmlns="">
and gets this response:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="" xmlns:xsi="" xmlns:xsd="" xmlns:wsa="" xmlns:wsse="" xmlns:wsu="">
			<wsu:Timestamp wsu:Id="Timestamp-ec9ba10a-728f-4376-9e53-d7f711177af7">
			<faultcode xmlns:q0="">q0:Security</faultcode>
			<faultstring>Security requirements are not satisfied because the security header is not present in the incoming message.</faultstring>
Does anyone have any suggestions on how to address this error?


David Brink
Eric Jones 14Eric Jones 14
Sorry for your troubles David. You will need to add a custom binding in your web.config or app.config depending on what type of project you are working on.

If you reference numbers 6-7 on this I believe it will resolve your issues.