Hi Luca,
The script that is calling getAllCampaigns() may need both the clients
email and the their account ID.
My script works like this:
//create short varaibles for Google API
$mccemail = MCC_USER; //constant set in an include file
$mccpwd = MCC_PWD; //constant set in an include file
$clientacc = $_SESSION['useremail']; //Clients Google Account Email
from session var
$clientid = $_SESSION['googleid']; //Clients Google campaign ID from
session var
$devtoken = GAPI_DEV; //constant set in an include file
$apptoken = GAPI_APP; //constant set in an include file
(...later on...)
//use the clients Google account ID stored in the dbase
$campaignObject = createCampaignObject($clientid);
$handle = array($campaignObject->getCampaignStats($startday,
$endday));
echo "<pre>";
print_r($handle);
echo "</pre>";
Where you would swap out getCampaignStats for getAllCampaigns.
Note the object being created is using the ID and NOT the email. The
client email was already used to authenticate with APIlity.
rwhite35
On Jul 2, 12:59 pm, LucaMago <l.magon...@blicomm.net> wrote:
> Hi, I’m writing because, from yesterday at 14.00 (more or less) we
> can’t no more use the apility service.
> Every time we try to use the apility we have this error:
> Message: The specified account is inactive.
> Code: 119
> We are using v.1.13.1 of apility, and the error comes out when we call
> the method getAllCampaigns(), while if we simply make a new istance of
> APIlityUser() there are no errors.
> We tried to change the account name, and its password but without
> success.
> Is important to say that the accounts that we tried to use, work if we
> connect to the account manager panel, where we manage our campaigns.
> We checked the developer and application tokens and they are both
> correct compared to the ones that are in the account manager in the
> apility section.
> We tried to set an invalid developer tokens and, correctly, it say
> that is incorrect.
> We tried to change the password, in the authentication.ini file, used
> to connect to the account manager but the error is always the same:
> error 119.
> We have enough credit to use the apility as the account manager says
> correctly.
> This is really a big issue for us and for our customers.
> Looking at the XML that the calls generate it seems correct, and the
> answer says, always, that the account is inactive generating a 500
> internal server error.
> What can we do?
> Thank in advance for your support
> Best regards,
> Luca