GET
/
embed
/
{hub_id}
/
users
/
{user_id}
/
integrations
/
{integration_id}
curl --request GET \
  --url https://platform.versori.com/api/embedded/v1/embed/{hub_id}/users/{user_id}/integrations/{integration_id}
{
  "id": "<string>",
  "name": "<string>",
  "imageUrl": "<string>",
  "variablesSchema": {},
  "description": "<string>",
  "isDeployed": true,
  "isActivated": true,
  "connectionTemplates": [
    {
      "id": "<string>",
      "connectorId": "<string>",
      "imageUrl": "<string>",
      "name": "<string>",
      "isUsed": true,
      "isPrimary": true,
      "authSchemeConfig": {
        "id": "<string>",
        "description": "<string>",
        "validationMessages": [
          {
            "text": "<string>",
            "severity": "info",
            "detail": [
              "<string>"
            ]
          }
        ],
        "schemeType": "<string>"
      }
    }
  ]
}

Path Parameters

​
hub_id
string
required
​
user_id
string
required

UserID references an End User in the Hub.

Most APIs support setting this value to either the internal Versori identifier or their external ID as determined by the organisation. The identifier_type query parameter is used to indicate which type of ID is being used.

​
integration_id
string
required

Query Parameters

​
identifier_type
enum<string>
default:external

IdentifierType indicates whether the user_id path parameter is a internal identifier created by Versori, or an external identifier. If the value is external, some endpoints also require the hub query parameter to identify the correct Hub.

Available options:
internal,
external

Response

200
application/json

OK

EmbeddedIntegration represents an integration that is available to an end user and contains all the necessary information for the UI to determine how the user should activate the integration.