In a nutshell, here is my stupid question: Just what exactly is the
"CLIENT_CUSTOMER_ID" that needs to be passed in the header of the GET
to pull the actual report? Believe me, I've looked all over to try
and find this defined.
The docs are a little vague on whether I need to supply the client
email and/or customer ID if I'm not using an auth token for an MCC
account ("If the authToken identifies an MCC account, specify exactly
one of these headers to generate a report for a client"). I normally
do not use MCC logins for API calls. In these cases if I only supply
the auth token for a non-MCC login, then I get the error below when I
do the HTTP GET to this URL
https://adwords.google.com/api/adwords/reportdownload?__rd=805527
!!!AuthenticationError.CLIENT_CUSTOMER_ID_IS_REQUIRED|||805527
If I supply the client email header var ("clientEmail") using the same
client email that I supplied when I retrieved the auth token, then I
get this error:
!!!ReportDefinitionError.INVALID_REPORT_DEFINITION_ID|||805527
even though the id is what was returned by the ReportDefinitionService
a few seconds earlier as mutateResponse.rval.id from request ID
5bf2504d0e7b5dcd8e97e302d050b619 to mutate ADD using the same auth
token.
>From how I read the docs, the V13 3-step process of
1. Request a Report,
2. Check on Report status until URL status is ready,
3. HTTP GET to URL from step 2,
is now in V2010 a 2-step process of
1. Mutate ADD report definition,
2. HTTP GET for report Definition ID from step 1.
It looks like a V2010 GET operation is only needed if I want to get a
list of the report definition IDs, but is not required for the actual
process of getting reports - is that correct? The "waiting" process
of V13's step 2 (which the adWords server generates the report) is now
in V2010 implicit in the HTTP GET, right?
Are report definition IDs tied to the account associated with the auth
token that did the Mutate ADD, or can they be used across accounts
(since the docs defined a report definition as only being the report
type, date range, fields, and predicates, and doesn't say anything
about the actual account whose data is being reported on)? In other
words, can I define a report then make multiple calls to the HTTP GET
url with that same report ID, but with differeing auth tokens to get
the same report layout for each of those accounts? Or do I need to do
the Mutate ADD for each of the auth tokens, with the same SOAP body of
the common report definition parameters, and then do the HTTP GET for
each pair of auth token and report definition ID?
thanks much,
-reed
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.blogspot.com
http://groups.google.com/group/adwords-api
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
