Skip to content

Get Telegram Integration by Unit

Endpoint used to get a Telegram integration by unit.

Terminal window
curl --request GET \
--url https://converflow.api.prod.toolzz.media/api/v1/telegram/integration/unit/{unitId} \
--header 'Authorization: Bearer TOKEN_HERE'
{
"data": [
{
"id": "uuid",
"botId": "uuid",
"unitId": "uuid",
"title": "<string>",
"isActive": true,
"botToken": "<string>",
"isTokenMasked": true,
"scope": "<string>",
"welcomeMessage": "<string>",
"createdAt": "<timestamp>",
"updatedAt": "<timestamp>",
"deletedAt": null
}
]
}

ParameterTypeDescriptionRequired
AuthorizationStringAccess token (“Bearer” must be before the token)Yes
ParameterTypeDescriptionRequired
unitIdStringUnit IDYes
KeyTypeDescription
data[]ArrayList of objects containing the Telegram integration settings.
data[].idUUIDUnique identifier of the configuration in the database.
data[].botIdUUIDIdentifier of the bot associated within the Toolzz AI platform.
data[].unitIdUUIDUnique identifier of the owning organizational unit.
data[].titleStringIntegration identifier name (e.g., “TelegramAI”).
data[].isActiveBooleanIndicates if the Telegram integration is active and operating.
data[].botTokenStringAuthentication token (Bot API Key) masked for security.
data[].isTokenMaskedBooleanConfirms if the token returned in the response is hidden.
data[].scopeStringBot’s scope of action (e.g., both, private, group).
data[].welcomeMessageStringAutomatic greeting message for new users.
data[].createdAtStringRecord creation date and time (ISO 8601).
data[].updatedAtStringDate and time of the last configuration modification.
data[].deletedAtString/NullLogical deletion date (Soft Delete), if applicable.

To access this endpoint, it is necessary to send a valid access token through the authorization header (Authorization) of the request. Additionally, the API is protected by other security measures to safeguard user data.

To access your access token, follow these steps:

  1. Log in to the ToolzzAI platform
  2. Click on “Settings”
  3. Click on “Access Token”
  4. Copy the access token

Access token page