--- title: "Integrate auto-launching the app" slug: "mas-5-ig-integrate-auto-launch-5-7-0" updated: 2026-04-22T08:46:55Z published: 2026-04-22T08:46:55Z canonical: "docs.onespan.com/mas-5-ig-integrate-auto-launch-5-7-0" excludeFromSearch: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Integrate auto-launching the app Users can launch the Mobile Authenticator Studio app and execute a predefined action by invoking a URL with the following format: ${scheme}://${actionName} Where: - ${scheme} is the custom URL scheme specified when the Mobile Authenticator Studio app is customized, in accordance with iOS and Android scheme policies. - ${actionName} can be one of the following: - `onlineactivationid` - `offlineactivationid` (standard licensing) - `actionid` The action name can be followed by the action parameters in the following format: ```plaintext $scheme://${actionName}? ActionParameterName1=ActionParameterName1Value&ActionParameterName2=ActionParameterName2Value ``` Action and parameter names are not case-sensitive. > If the URL format is incorrect, the app will display an error message and terminate. Unknown parameters are silently ignored. ## Online activation When the ${scheme}://MyOnlineActivationId URL is invoked, it launches the online activation with the MyOnlineActivationId identifier. This action supports the following parameters: - `Identifier`. This is the registration identifier. It is an alphanumeric string, limited to 40 characters. - `ActivationPassword`. This is the authenticator activation password. It is an alphanumeric string, limited to 40 characters. All parameters are optional. ## Offline activation (standard license activation) When the ${scheme}://offlineactivationid URL is invoked, it launches the offline activation for the Mobile Authenticator Studio app. This action supports the following parameters: - `SerialNumber` The authenticator’s serial number. It consists of three alphabetic characters and seven numeric digits. > Do not use a serial number suffix (e.g. “1280189”) instead of the full serial number (e.g. “FDM1280189”) in the activation URL. The serial number prefix will be retrieved from the static vector. Thus, the serial number prefix can differ from the static vector that is hardcoded in the mobile app (e.g. “FDL”) and the authenticator BLOB used by the server (e.g. “FDM”). In this case, the authenticator instance will be properly activated, but the generated authenticator responses (i.e. one-time password and signature) will be invalid. - `ActivationCode` The authenticator activation code, a hexadecimal character string. - `ERC` The authenticator event reactivation counter. This value can be modified once it is displayed for validation. All parameters are optional. ## Authenticator actions When the ${scheme}://MyActivationId URL is invoked, it launches the offline activation with the MyActivationId identifier. This action supports the following parameters: - `SerialNumber` Serial number to use if the authenticator application is configured in the multi-instance mode. - Data fields 1-8 to sign: - `dtf1` - `dtf2` - `dtf3` - `dtf4` - `dtf5` - `dtf6` - `dtf7` - `dtf8` - `challenge` > The `challenge` and `dtfx` parameters cannot be combined in the same URL.