The Application ID is a string that identifies your Application when interacting with Latch. It’s automatically assigned to your Application when you create it and cannot be changed. You can check your Application ID editing your Application in the My Applications section of the Latch Developer private area.

All the identifying Application IDs are associated with a Secret, which is used to sign all the applications from your Applications in our API. Make sure that the security of the Secret is always protected, don't share the secret with anyone and don't distribute it, either the code or the set-up. You can change it whenever you want by pressing the Renew button.

The operations are the means by which you can make sure that your users protect and unprotect the different functions of your service. For example, if it's an online banking service, you can have one operation associated with the authentication process, another associated with making international transfers and a third for transfers over a certain limit. Your users will see three entries under your service name in their mobile apps that they can protect independently.

It is a lock option that will lock the service or operation automatically each time it is used by endusers. This security option can be activated as compulsory or optional.

Each operation has its ID and name. You can also have suboperations (within the limits established in the chosen subscription), an OTP (not in every case because some of the Latch plug-ins don't support it), and an Autolock by use. These last two options are not available in the Community mode subscription.

It isn't compulsory, but we do recommend it since these are the data which will be available to the end users if they have a problem with the service itself or the operation. These details will be displayed in some of the critical notifications that Latch users will receive, for example when there is an unauthorized attempt to access the service or operation.

The icon is stored in the device's cache. The new icon will not be visible until this cache is updated. This depends on the operating system on the mobile device where Latch has been installed.

You need to create an Application for your service in the My Applications section of the Latch Developer private area. Once you have an Application ID and Secret, you can make calls to the Latch API. To simplify this task, we provide a web service API, SDKs for most common languages, and even plugins so that you don't need to write any code for the most common platforms. You will need to make slight modifications to your code to call the Latch API for each operation that you want your users to be able to lock or unlock.

A button will appear on the plug-in download page where you can download the corresponding integration manual. Also, in the Developer area, under the heading Documentation and SDKs there is a section called Resources, where you can download manuals in English and Spanish giving a step-by-step explanation of how to integrate the Latch plug-in with the service in question. This section will be extended as new plug-ins are created.

The new pairing service will appear on all the devices. If it is unpaired it will disappear from all the devices.

Not at all. Your service will disappear from the list of pairing services the users have in the application so they will not be able to use Latch as an additional protective measure. From this moment they will access your service just as they did before you integrated it with Latch.