Hello,
Can write_app_proxy be listed in the optional_scopes? Based on the documentation and the fact that “For merchant stores that don’t accept the new scopes, we’ll backfill the scope on our side“, I assume the answer is no.
My app provides an API endpoint that merchants can use to dynamically access data via the app proxy and display such data on their storefront. The majority of the app’s users don’t use the feature and probably don’t know what an app proxy is. However, I share concerns with other developers that the wording isn’t very clear about the effects of granting the permission When exactly do I need the write_app_proxy scope? .
I appreciate it’s late, but would it be possible to provide some additional context to the data access prompt? It would be helpful to highlight that in the past, apps could provide the same functionality without the access scope, and we haven’t suddenly changed how our apps function.
Thank you