Judge.me uses OAuth to help App Developers access its API, allowing Apps to get stores data from Judge.me. It lets stores give certain Apps permission to access their data on Judge.me.
This guide shows a simple example of how the OAuth process works for Stores, focusing on their part of the interaction.
Scenario: Store A and App B Interaction
Picture this: store A uses Judge.me, a platform storing its data. Now, store A wants to use a cool feature in App B that needs access to its Judge.me data.
This might mean showing Judge.me reviews in App B's widgets. To make it happen, store A just needs to give App B permission to use its Judge.me data.
OAuth Authorization Process for store A
Access Request: App B has a dedicated section on its website with a button. Store A uses this button to give App B permission to access its Judge.me data.
Starting Authorization: Store A clicks this button on App B's website to begin the authorization process.
Redirect to Judge.me Page: Store A is then sent to Judge.me's authorization page through a special web link. This link contains specific details, such as App B's ID, where to send the response, what permissions are needed, and a unique identifier. Here's how the link looks:
Login (if required): If store A isn't logged in, they'll be asked to log in to confirm their identity.
Permission Granting: After logging in, Judge.me will show a screen asking store A for permission to let App B use their Judge.me data.
Reviewing Permissions: Store A checks the permissions App B is asking for. To say yes, they click "Authorize." To say no, they click "Cancel."
Access Authorization: Clicking "Authorize" lets Judge.me grant App B permission to access Store A's reviews.
Back to App B: Store A returns to App B's platform, ready to use the Judge.me data.
By following these steps, store A allows App B to smoothly access Judge.me data, improving the integration within App B's features.