AdWords requesting access to account for API usage
We have an MCC that we have used (for years) to exclusively to for attaching client accounts form multiple clients mostly so we can use the adwords API to get reporting. I have not done any of this work for a while as we have had other people doing it but it fell to me this time. So I requested access of a client via the MCC. The response I received required me to setup a new google account - there seemed to be no other option that would work - this is NOT how I have done things in the past. Once I set it up the account it did provide me with information for the specific client requested but it is no longer associated with the MCC and the account does not have API access so the whole thing is of no use. How do I get this client associated with the MCC so I can get API using the tokens etc already setup in the MCC or if that cant be done, what do I need to do to get this where the account is linked into the MCC so that I will have API access. Also what kind of access do I now need for API access. The role given was manged read access - what role do I now need
Thanks for any help
Re: AdWords requesting access to account for API usage[ Edited ]
July 2015 - last edited July 2015
there is no need to link any account to any
mcc for api-access to that account's data.
two pieces of data are required to make an api-call:
(1) a one-time developer-token for using the api and
(2) per-call account-credentials for accessing a specific account.
an approved developer-token allows access to the api --
the authorized-credentials allows access to an account.
if the developer-token has been approved and is currently activated
then, the per-call account-credentials for accessing a specific (client)
account is required.
generally, the client (user) must give permission to the application
to access their account information -- by granting authorization,
typically via oauth2.
most api client-libraries (python, perl, etc.) have built-in oauth2 flows.
of course, having the client's account under the same mcc as the
developer-token can help simplify setting user-access-levels and
the per-call authentication process -- but is in no way required.
the api-forum is currently here: