Example 1:
InfoSelector selector = new InfoSelector();
selector.setApiUsageType(ApiUsageType.UNIT_COUNT);
selector.setDateRange(new DateRange("20100101", "20100201"));
ApiUsageInfo res = service.get(selector);
always return 0 costs, while V13 Version getUnitCount(startDate,
endDate) works fine.
Example 2:
InfoSelector selector = new InfoSelector();
selector.setClientEmails(new String[] { "<valid client email>" });
selector.setApiUsageType(ApiUsageType.UNIT_COUNT_FOR_CLIENTS);
selector.setDateRange(new DateRange("20100101", "20100201"));
ApiUsageInfo res = service.get(selector);
throws an error [ApiUsageError.INVALID_CLIENT_EMAIL @ selector] also
the specified email is a valid account in the mcc-acount.
Any suggestions?
Thanks
Ralf
By the way. Sample Code for Java is still for V200906 and not all
Services are included.
One of the caveats of the new InfoService is that it currently only
works if your email and password used to generate the authToken is for
the MCC account that owns the developer token (has the AdWords API
Center tab in the web interface). Please ensure that you are using
this MCC user when generating your authToken and try again.
Best,
- Eric Koleda, AdWords API Team
we always use the MCC-user to get the auth-token and we use the email
of the specific account in the soap-header of the services.
we tried the InfoService also with the MCC-user in the soap-header -
but both variants do not work.
Thanks
Ralf
On Feb 3, 8:25 pm, AdWords API Advisor <adwordsapiadvi...@google.com>
wrote:
> Hi Ralph,
>
> One of the caveats of the newInfoServiceis that it currently only
> works if your email and password used to generate the authToken is for
> the MCC account that owns the developer token (has the AdWords API
> Center tab in the web interface). Please ensure that you are using
> this MCC user when generating your authToken and try again.
>
> Best,
> - Eric Koleda, AdWords API Team
>
> On Feb 2, 10:20 am, "ralf.s" <ralf.sa...@googlemail.com> wrote:
>
>
>
> > We still get have problems with theInfoServiceof Version V200909.
When using the v200909 InfoService you need to ensure that you aren't
setting the clientEmail or clientCustomerId headers in the request.
Also, the MCC user you are using must be the same one that owns the
developer token.
Do you have the SOAP XML from these requests? I'd like to follow up
in the internal logs to see if I can track down the issue.
Best,
- Eric