We’ve recently upgraded from V9 to V10 and are experiencing an issue where the accounts are no longer available after Authenticating the API connector through our 3rd party vendor (Adverity) application. Prior to the upgrade, we were able to see which accounts were associated with the connector we created.
We are able to authenticate the account successfully but are unable to see any associated accounts. Connectors that were previously authenticated, before the update, we can still see the accounts. Once we authenticated again, after the upgrade, the accounts disappear.
We do have Admin Access to multiple accounts in the Ads UI.
Our specific error: TwitterAccountException: Action_Not_Allowed - This user does not have permission to read campaign data for account xxxxxx (HTTP 403).
Can you help us understand what specifically is required for our account so that we are able to see the accounts using V10?
Related to the announcement:
[CHANGED] Non-advertiser accounts will no longer be returned by the GET accounts endpoint
- Engineering Effort: N/A
- Most relevant to: Developers working with Analytics and Media Studio accounts not fully set up for Twitter Ads
Moving forward, partners working with accounts not fully set up for Twitter Ads on the Ads API will no longer see those accounts returned from the GET accounts endpoint in v10. This functionality will still remain in v9.
- In particular, this may affect Analytics accounts that are not fully set up for Twitter Ads
on the Ads API and fetch organic analytics for their clients.
This change was made to maintain consistency across the Ads API. As an advertising-specific API, we want to ensure all partners are set up properly with an advertiser account in order to leverage its services.
In order to continue to be able to access these ads accounts, the advertiser must complete the one-time setup via ads.twitter.com . Instructions can be found here .
