Test the app authorizations you create, before making them live for your users. Besides, testing authorizations you can also test Endpoints and Actions. Testing an activity and an endpoint will only work if the user account is properly connected. So, it is recommended to test your authorization first and then move to test other modules.
A little about Authorizations
When a user sets up integration with your app using our widget, they need to authorize Integry to access the API on their behalf.
When creating these authorizations, you can test them under the Authorization tab in your App's menu. Learn more about Authorization and how to create one. We support the popular authorization types, details.
Let’s say you have created the OAuth2 authorization for your app MyApp, as shown below.
Under the list of authorizations, you can view the tab, Connected Accounts as shown below.
This is where you can test if the authorization you created works properly using an account on the app. Click on the Add New Account button. You will be redirected to the Grant Screen (in case of OAuth only) as shown in the example below. In the case of API-Key, it will open a popup asking for API Key etc.
Enter the credentials and you can start testing. You can view the account you have added under the Connected Accounts tab as shown below.
The Test icon on the right side lets you test whether the account is connected. If you have properly configured your OAuth2, you will see a Connected label when you click the Test icon as shown below.
What if the 'Connected' label does not appear when you test an account?
Well there can be scenarios when the authorization is not properly configured or the details you provided are incorrect. If you haven't properly configured OAuth2.0, the Grant Screen will show an error. In some cases, you will view a Not Connected label in front of your account as shown below.
The possible reasons for such cases can be as follows:
- The User Information Endpoint was not configured properly
- The Access Token Endpoint was not properly configured in-case of OAuth2.0
- You might have entered incorrect API-Key value while connecting to your account. Add the account again with correct values.
If the authorization works perfectly, you can test your endpoints and actions.