Ubisecure is API-first. If that statement leaves you none the wiser, read on to learn 3 key things – what are APIs, what are Ubisecure’s APIs and why do we have this business model?

What are APIs?

API stands for Application Programming Interface. Technically speaking, an API is set of protocols that define possible interactions between apps. In less technical terms, APIs tell apps how to co-operate with each other and move information between those apps automatically. Essentially, they integrate two (or more) apps.

Using APIs to enable very specific functionality in your systems removes the headache of having to build them from scratch yourself. Simply ‘plug in’ new APIs and you’ve got expertise on demand, as explained in  this other Ubisecure blog – ‘The rise of identity APIs in the API economy’.

Identity APIs

Our identity APIs are built to enable CIAM (Customer Identity & Access Management) functionality. This means that our customers use our APIs to easily implement first-class log in and profile management components on their services, to provide a secure and seamless standards-based experience for their customers. Using our APIs removes the need to build this functionality from scratch – they simply add expertly-built features to their existing technology. You can check out some of our real-life customer use cases here.

APIs can also be combined with other APIs. For example, a key aspect of any CIAM project is choosing which identity authentication methods to offer customers accessing the service(s). There are a multitude of options, from social verification (e.g. ‘log in with Facebook’) to strong identification through Bank IDs (identification via bank account), National IDs and even mobile IDs. Because of the large variety of options available for authentication (see image below), we added the Authentication Adapter. This is a microservice to enable the rapid and seamless addition of other identity providers.

Authentication Adaptor


RapidLEI is a Ubisecure service that automates the LEI creation process to deliver LEIs quickly and easily. For a quick explanation of what LEIs are and how RapidLEI is disrupting this exciting and essential industry, check out this short video:


We have now launched the industry’s first LEI API from an accredited LEI Issuer (that’s us), which will allow third party developers to add same-session LEI issuance into applications and workflows.

Why API-first?

Companies come to us because they have external user identity management requirements – as most companies of a certain size do. What’s not common to each customer is the industry, local/industry regulations and the sort of system(s) they’re using. Although we find many use cases to be similar, we often find that no two projects are exactly the same.

By saying we’re API-first, we’re saying that our priority is to provide greater value and efficiency for our customers in selecting certain APIs for their own applications, to deliver more effective (and safer) identity management to their customers.

The biggest value for being API-first in our RapidLEI service is to allow our partners to build it into their own systems. So there’s no need for partners to send their customers to our site for LEI issuance, or to apply/manage the LEI on their behalf. For more information on how the API can be used, check out this blog – Announcing the RapidLEI API – same-session LEI issuance for third party application developers.

Are you interested in using our Identity Server or RapidLEI APIs? Send us a message.