Has anyone had namespace issues using the PHP SOAP Extension on the
Sandbox?
Production is a single namespace. The Sandbox WSDL has namespace
paths to production, with the soap address in the sandbox. This seems
to cause multiple namespaces in the SOAP header when using PHP's SOAP
extension. T
The Google Sandbox documentation states the Application Token is
ignored.
When using Apility, the ApilityManager constructor checks for presence
of the application token as well as other vars to decide whether to
use those vars or default to the authentication.ini file.
If you are loading your S
m/questions/589228/sending-a-soap-header-with-
>
> --Stan
>
> On Jun 23, 12:12 pm, jrj10 wrote:
>
> > I am using PHP's built in SOAP extension. My test code works in
> > production and I can pull down campaign info from our live account.
> > The same cod
I am using PHP's built in SOAP extension. My test code works in
production and I can pull down campaign info from our live account.
The same code fails when attempting to work in the Google Sandbox.
(Error is: The request did not contain a header named 'email'.)
Additionally, I can take the cred