Deprecation of the default namespace in the AdSense Management API
2014年2月20日星期四
TL;DR Projects using the AdSense Management API should now check for accounts with multiple AdSense/AdX accounts and let users pick instead of using the default namespace, as it will be disabled for some accounts.
API users with access to more than one AdSense or AdX accounts will receive an error when using the default namespace due to cases of ambiguity. We expect a very small percentage of users to have this problem, as this functionality is restricted to a limited set of accounts.
To avoid complications, make sure you're not using the default account namespace
The flow you should always use from now on is:
API users with access to more than one AdSense or AdX accounts will receive an error when using the default namespace due to cases of ambiguity. We expect a very small percentage of users to have this problem, as this functionality is restricted to a limited set of accounts.
To avoid complications, make sure you're not using the default account namespace
adclients.list
, adunits.getAdCode
, etc. and specify an account ID for every call. For that, use accounts.adclients.list
, accounts.adunits.getAdCode
, etc. You’ll find the whole list of calls in the API reference pages.The flow you should always use from now on is:
- Authenticate
- Call
accounts.list
- Show a publisher account picker if there's more than one account
- Do the rest of the requests using the account ID