Before we dive deeper into advanced application types and configurations, it's worth taking the time to better understand the basics of inTandem applications.
When creating applications you'll constantly come across several terms, so it's better to understand these basic terms before you begin.
An integration point refers to the place in the UI that your app integrates with. For example, if you create an app that creates a new sub-menu item, the integration point of your app is the menu.
Applications that have an integration point in the UI must be assigned to the relevant accounts (or to the entire directory) in order to appear in the UI.
Applications are essentially abstract entities that have the ability to make API calls on behalf of specific accounts. However, if an app needs to have a UI appearance (like an app that adds a menu item), this app needs to be assigned to the requested account.
The name of your application. Applications that have an integration point in the UI will use the application name to present themselves. For instance, if you create a payment gateway application, the name of the payment gateway in the payments settings page will be the app name.
The redirect URI relates to the OAuth2 protocol which requires you to specify a redirect URI that users will get redirected to after the authorization is approved. Since OAuth is a major part of any application, it is a mandatory field for creating new applications within our platform.
Trusted apps will not require users' permission during the OAuth flow, while non-trusted apps will require the users' grant, by opening a window asking the user to allow the app access to their account within our platform.
Applications can specify a list of countries that can load the app, based on the country name specified at the account level. This can be a very useful solution if you want your app to only be available in certain countries, due to regulation differences, etc.
Applications that have no supported_countries list specified, will be available to all geo-locations.
client_id and client_secret
Both of these parameters are returned in the response body of your "create app" request. It's highly important to store these in your database as they can't be retrieved again at a later time.
You'll need to use the client id and client secret during the OAuth process.
The app_code_name is also returned in the body response when creating an app. It is used as the app identifier (even though there's an app id param as well) in all application-related APIs.
Updated about 1 month ago