I am attempting to expand scope for an existing app that I own, but am unable to scope billing and billing plan read-access.
This is an Account-Level S2S OAuth app.
I am able to see a full range of scopable billing fields on other apps I own that are Account-Level S2S OAuth apps.
I am able to create a brand new App with identical config settings that has access to the billing fields I’m looking to scope.
Any idea what might be the bottleneck here? IIRC there should not be any additional dependencies for these fields as long as the creator of the app has Master account access.
I previously asked questions on this forum about the billing API endpoints and was told they are intended to be used by master accounts to manage their sub-accounts.
I’m guessing you are witnessing different functionality in one account and/or app versus other account/app due to the fact one is master and the other is not.
Thanks @desautelsj - I had consulted that article before posting this one.
Both apps shown are owned by the same user (me) and have the same level of access.
Also, no issues with new apps, which is what’s throwing me. Theoretically, I could just build a new one and have everything I need, but I’d prefer to keep existing keys in place.
The only difference I can spot is that the “Information” section of the app config never gets a check-mark, despite having all required info and saving changes:
Good shout - looks like it’s about 2 months older than granular scopes are.
There are no migration options showing for my S2S app’s classic scopes and after browsing around some other threads on this, it seems like I’ll need to create a new app after all.
