This introduction includes high-level instructions on building the front-end component of your integration hub within your own application.

​
Choosing your embedded implementation

Before continuing, it’s worth understanding two approaches to building your integration hub.

​
Full Client-Side

In this approach, your integration hub is built entirely in the client-side code of your application. This is the simplest (and quickest) way to get started for most applications, however some users may prefer implementing some server-side logic to facilitate the integration hub, in which case the hybrid approach is available.

​
Authentication

When using the fully client-side approach, you will need to authenticate your users against Versori APIs using Signing-Key tokens.
You should not expose your Signing Key to your users. This key should be kept secure and only used in your server-side code to issue JWTs.
This approach involves implementing a new API endpoint in your own application which can authenticate your end user and issue a JWT signed with a Signing-Key. This token can then be used to authenticate your user against Versori APIs, and they will only have access to manage their own activations to your integration hub.
We are working on providing reference implementations for this endpoint in multiple languages/frameworks. If you would like to discuss this further, please reach out to us.

​
Hybrid Client-Side and Server-Side

In this approach, your integration hub is built using a combination of client-side and server-side code. This allows you to pick and choose which parts of the integration hub are built in the client-side versus the server-side to suit your application’s requirements.

​
Pre-requisites

Before building your integration hub, you will need to have the following:
  • Your organisation ID, obtaining this is covered in the concepts section.
  • At least one deployed Integration created in the Versori platform.
  • Chosen an implementation method covered above.