curl --request GET \
--url https://platform.versori.com/api/embedded/v1/hubs/{hub_id}/users/{user_id}/connections \
--header 'Authorization: Bearer <token>'{
"totalCount": 123,
"next": "<string>",
"prev": "<string>",
"connections": [
{
"id": "<string>",
"name": "<string>",
"createdAt": "2023-11-07T05:31:56Z",
"updatedAt": "2023-11-07T05:31:56Z"
}
]
}ListEndUserConnections returns all the Connections for the given End User.
The result may be filtered by hub_connector_id to only return connections for a specific Hub Connector.
curl --request GET \
--url https://platform.versori.com/api/embedded/v1/hubs/{hub_id}/users/{user_id}/connections \
--header 'Authorization: Bearer <token>'{
"totalCount": 123,
"next": "<string>",
"prev": "<string>",
"connections": [
{
"id": "<string>",
"name": "<string>",
"createdAt": "2023-11-07T05:31:56Z",
"updatedAt": "2023-11-07T05:31:56Z"
}
]
}Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
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.
Search is a string that is used to filter the list of Connections. The search string is matched against the name.
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.
internal, external