To get the merchant information using our rest api, you will need to follow our oauth flow to retrieve an access token for the merchant as explained
here. Using that access token, you can get details about the merchant associated with that access token as demonstrated in our documentation
For each app, Clover asks what permissions a developer needs, like employee read/write permissions. This not only lets Clover see what data an app requires, but also lets individual merchants decide what permissions they want to give an app.
For example, if a merchant is uncomfortable giving their customer data to third-party apps, they can choose not to download apps that require those permissions.
We want to protect our merchants’ data, so we don’t let third-party apps access any merchant information unless:
The app specifically requires certain permissions to function AND
The merchant consents to giving this information by downloading the app or logging into their account through OAuth.
can receive a merchant’s data as long as they access your app through OAuth. Unfortunately, you won’t be able to do this until you use the Production environment and your app is approved, as Sandbox apps are not available for live merchants.
Sandbox is just a place to test your app and make sure everything is working. You can implement the OAuth flow, like Lauren explained, and as long as you’re correctly connecting to your test merchant through OAuth, you should be able to connect to other merchants in the same way once you move your app to Production and it’s approved.