ListIntegrationConnectors returns all the Hub Connectors for the given Integration.

This API should not be exposed to End Users via the embedded UI since it includes connectors which have not
been published.


List Hub Connectors

AuthSchemeConfig defines how a Connector implements the AuthScheme in order to fulfil its 
authentication requirements. This is purely the configuration and not the actual credential 
which is used to authenticate. The credential uses this configuration to determine how to 
authenticate.


Name is the query parameter/header/cookie name which will be used to send the API key.

AuthSchemeConfigAPIKey defines how a Connector uses an API key credential to authenticate with the system.


AuthSchemeConfigAPIKeyIn defines the location of the API key in the request.


Description enables users to distinguish multiple configurations which use the same 
schemeType.


ID is the unique identifier of the AuthSchemeConfig, this is generated by the client and
only requires to be unique amongst the elements of the array in which is it contained.


ValidationMessages is a list of messages which are generated when the AuthSchemeConfig 
is validated. This is typically used to provide feedback to the user when they are 
creating or updating the AuthSchemeConfig.

This field will be ignored if sent to the API.


AuthSchemeConfigBasicAuth is a placeholder object with the schemeType set to `basic-auth`. There is no other
configuration required.


AuthSchemeConfigCertificate is a placeholder object with the schemeType set to `certificate`. 
There is no other config required


AuthSchemeConfigHMACAlgorithm defines the hashing algorithm to use when generating the HMAC signature.

AuthSchemeConfigHMACInputs defines what parts of a HTTP request are consumed to generate the HMAC signature. Some systems
only generate the signature from the request body, others may include the URL. The order of this array
defines the order in which the input is fed into the hashing function.


Name is the query parameter/header/cookie name which will be used to send the signature.

AuthSchemeConfigHMAC defines how a Connector uses an HMAC credential to authenticate with the system.

This may be used on outbound requests to sign the request body, however it is more commonly used on inbound
requests (i.e. from Webhook Triggers) to verify the sender of the request is allowed to invoke the Trigger.


AuthSchemeConfigHMACIn defines where the signature should be set on requests.

AuthSchemeConfigNone is a placeholder object with the schemeType set to `none`. There is no other configuration
required.


AdditionalAuthorizeParams is a URL-encoded query string which should be attached to 
the AuthorizeURL when the user is redirected to the OAuth 2.0 authorization 
endpoint.

This value is only used by the UI to drive the default values when connecting, the 
API to `InitialiseOAuth2Connection` can be provided a different value if required.


AdditionalTokenParams is a URL-encoded string following the 
`application/x-www-form-urlencoded` mime-type, which can be used to pass additional
parameters to the OAuth 2.0 token endpoint within the request body.


AuthorizeURL is the URL which the user will be redirected to in order to authorize 
the application.


DefaultScopes is the list of scopes which will be requested by default when the user
connects the Connector. This is useful for Connectors which require a specific set 
of scopes to function correctly.


MTLSCredentialID is the unique identifier of the Credential which contains the 
client certificate and private key to be used as part of the mTLS connection. 

This may be unset when creating a connection, in which case if `mtlsEnabled` is 
true, then the API will find an associated AuthSchemeConfigCertificate and link 
them automatically.


MTLSEnabled is a flag which determines whether the Connector should use Mutual TLS 
(mTLS) to authenticate with the OAuth 2.0 token endpoint. This is useful for 
Connectors which require a higher level of security.


Scopes is the list of all OAuth2 scopes which the application supports. The user 
will be allowed to choose which scopes to request when configuring the Connection.


TokenURL is the URL which the application will use to issue an access token.


AuthSchemeConfigOAuth2 defines how a Connector uses an OAuth2 credential to authenticate 
with the system. This is to be used for all OAuth 2.0 flows which require a client ID and 
client secret as part of the Connector's configuration. Connectors which use the 
`client_credentials` grant type, where the user provides the Client ID  and Client Secret at
the point where they connect, should use the `AuthSchemeConfigOAuth2ClientCredentials` type 
instead.


AuthSchemeConfigOAuth2GrantAuthorizationCode contains grant-specific configuration for the 
`authorization_code` grant type.

How the API manages changes to this configuration is as follows:

- CredentialID and OrganisationID are not set, a new credential is created containing the
  sensitive information and the non-sensitive information is updated in the database.  
- Otherwise, both the credential and the database are updated using JSON Merge Patch, with
  undefined properties not being updated.
- Any other permutation will result in a 400 Bad Request.


ClientID is the OAuth 2.0 client's identifier. This is not a sensitive value and may be 
presented to the user in plaintext.


ClientSecret is the OAuth 2.0 client's secret. This is a sensitive value and will not be
displayed to the user.


CredentialID is the unique identifier of the Credential which contains the client ID and
client secret to be used as part of the `password` flow.


OrganisationID is the unique identifier of the Organisation that owns the Credential. 
This can be different to the Connector's OrganisationID since some may be imported from 
Versori's public library.


AuthSchemeConfigOAuth2GrantPassword contains grant-specific configuration for the `password` 
grant type.

How the API manages changes to this configuration is as follows:

- CredentialID and OrganisationID are not set, a new credential is created containing the
  sensitive information and the non-sensitive information is created/updated in the 
  database.  
- Otherwise, both the credential and the database are updated using JSON Merge Patch.
- Any other permutation will result in a 400 Bad Request.


ClientID is the OAuth 2.0 client's identifier. This is not a sensitive value and may be presented to the 
user in plaintext.


ClientSecret is the OAuth 2.0 client's secret. This is a sensitive value and will not be displayed to the 
user. It may be populated when updating the Credential.


OrganisationID is the unique identifier of the Organisation that owns the Credential. This can be different
to the Connector's OrganisationID since some may be imported from Versori's public library.


ErrorField denotes a field which has an error.

Field is the name of the field which has an error, this may be a path to a nested field, including array
elements. The format of this field is of the form: "field1.field2[0].field3"


Message is the error message for this specific field.

A Hub Connection Template is a lightweight wrapper around a Connector from Connect API, but includes additional
information to make embedding the integration simpler.

Versori-users do not need to establish connections in an integration. These are connected to
by end-users when they activate the integration from the embedded integration hub.


ConnectorID is the unique identifier of the Connector.

ID is the unique identifier of the Hub Connection Template.

ImageURL is a URL to an image/icon that represents the connector. This image is used within the 
integration tile displayed in the embedded UI.


IsPrimary indicates that this is the primary connections on the hub.

IsUsed indicates that this connection template is in use by the hub.

name denotes the name of the Connector that the template is wrapping.


Message is a message to be displayed to the user to indicate some information about the
preceding request.


Details contains additional information about the message. This is intended to be used
to provide more information about the message, such as a list of validation errors.


OAuth2Scope represents a single scope which can be requested by an OAuth2 application.


Description describes the scope in human-friendly terminology. This text may be 
displayed to users via a help tooltip or similar.


Name is the name of the scope as determined by the application to which this Connector 
is connecting to.


HubConnectionTemplatePage is a paginated list of Hub Connection Templates.


Authorization

Versori User Documentation

API Reference

Home

Integrate

Embedded

Welcome to the Versori Platform documentation.

Welcome

Introduction

Connect your APIs to the Versori Platform.

Overview

Learn about the protocols used by the Versori Platform.

Protocols

Authentication Methods

Actions

Triggers

Provide credentials for a Connector to facilitate Versori to interact with an external system.

Connections

Build integrations between your systems with Boards.

How It Works

Creating a Hub

Quickstart React

Quickstart

React SDK

Build integrations between your internal systems.

Boards are the entrypoint to building integrations.

Select one of the following APIs to get started

Learn how to authenticate with the Versori Platform.

Authentication

Our next-generation API for connecting to your external systems.

Our next-generation API for exposing Versori-powered integrations to your users.

Organisations API provides access to manage your Versori Organisation.

CreateSigningKey creates a new Signing Key for the Organisation. 

This API creates a new RSA key pair, storing the public key and returning the private key. The private key must 
be kept secure and should not be shared publicly as it has the ability to sign JWTs which can be used to 
authenticate to Versori APIs on behalf of your Organisation (or scoped to a specific End User within 
Versori Embedded).

If the private key is lost, it cannot be recovered and a new key pair must be generated. In this scenario, it is
the Organisation's responsibility to delete the Signing Key from Versori so that any JWTs signed by the lost key
are invalidated.


Create Signing Key

ListSigningKeys returns a list of all Signing Keys for the Organisation.


List Signing Keys

DeleteSigningKey deletes the signing key for the Organisation.

Any existing JWTs signed by this key will be invalidated and will no longer be accepted by the Versori platform.


Delete Signing Key

GetPublicKey returns the public key for the given Signing Key ID. This can be used to verify JWTs signed by an 
Organisation's Signing Key.


Retrieve public key

Proxy API enables authenticated requests through Connections in the Platform.

Use Cases

Endpoint

Welcome to the user documentation for the Versori Platform

Core Concepts

Within Switchboard, apps are the external-system nodes that you use to build out your integrations.

Apps

Boards

The Board Editor is your main tool for creating and editing boards. It is a visual tool that allows you to create and edit boards by dragging and dropping components onto the board.

Board Editor

The Hubs SDK is a tool that allows the users of your Product to integrate into different Apps you have configured in the Versori Platform.

Hubs SDK

Learn how to use Actions to automate your workflows.

The transformer action is a drag and drop action that allows you to transform the data in your workflow.

Transformer

The Databuilder allows for familiar form based templating and transformations

Databuilder

The filter action allows you to filter the resulting data based on a series of conditions.

Filter

Datamapper provides storage within Switchboard for remembering cross-system references to different entities.

Datamapper

The Batch action allows you to aggregate requests into a single output format.

Batch

The Delay Action is used to delay the execution of the next node in the workflow.

Delay

The Splitter Action accepts a List input and splits each item to be processed individually.

Splitter

The Trigger Action is used as a startpoint within your flows, to trigger requests either manually or on a schedule.

Trigger

Boards are built from Apps, and Actions in a drag-and-drop interface.

How to create a Board, an use the Board Editor

Multiple methods of connecting your apps are available.

How to Connect to your Apps

When building your integrations - you can add your operations from different systems, and provide further configuration.

How to add a Webhook Listener into your Integration

Selectors provide an intuitive interface for plucking data from previous steps in your flow, to be used within your requests and actions.

How to use Selectors to template data within your Integrations

The Hubs SDK enables users to authenticate and onboard into external integrations that are connected to your product

How to use the Versori Hubs SDK

Preview the output of a transformer. This endpoint is useful for testing a transformer before creating an integration.


Preview the output of a transformer.

Retrieve a signed URL for uploading a schema specification


Upload a schema document based on a source URL. The server will download this URL and upload to object
storage automatically.


SchemaInfo processes the schema referenced by the provided URL and returns information to allow a user to create
an App.

Deprecated: This endpoint is no longer supported, users should create a Schema using the `CreateSchema`
(POST /organisations/{organisationId}/schemas) operation, and use the `GetSchemaInfo` operation to retrieve
this information.


Retrieve a signed URL for uploading assets


API Reference

Connect API

Embedded API

Organisations API

Proxy API

List Hub Connectors

Path Parameters

Query Parameters

Response