Improved self-authorization workflow for private developers #3111
jenilew
announced in
Announcements
Replies: 1 comment 1 reply
-
I know this is old, but I am hoping someone can help. I have a Private SP-API app and I am trying to authorize it to a different Seller Central account (i.e., not the account that holds the developer profile). It has always worked for me in the past, but now after I sign in to the second account, the Authorize button is simply not there. Did something break? Is there a workaround? I am pretty desperate at this point. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi All,
We are excited to announce improvements to the self-authorization workflow for private developers!
Private developers can now complete self-authorization across their regional accounts and other seller accounts they own, from the same page instead of switching between accounts from Seller Central.
As part of the experience, developers can authorize their apps across their regional accounts and retrieve a self-authorization (refresh) token from the same authorization page.
This change is intended to simplify managing your self-authorization (refresh) tokens across acounts and across regions.
In Seller Central, go to Apps & Services, then Develop apps. Click the down arrow next to Edit Apps and click Authorize to view the new one-stop authorization page.
Which marketplaces are affected?
All marketplaces are affected.
Who is affected?
Private developers with more than one regional account or more than one seller account are affected.
What action is required?
No action is required.
Best regards,
The Selling Partner API team
Beta Was this translation helpful? Give feedback.
All reactions