Lists channel types this integration provides.
Catalog metadata, not per-tenant data. Slack provides `channel`/`im`/`group`; Telegram provides `chat`; integrations that don't deliver messages return an empty list. Drives the participant address picker's input hints and the future integration tab's Channels section.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The integration ID.
The tenant identifier
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/integrations/string/channels"[
{
"id": "string",
"displayName": "string",
"description": "string",
"addressPlaceholder": "string",
"addressFormat": "string",
"addressHelpText": "string"
}
]{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Initiates an OAuth flow for application-level (agent-level) integration auth
Used when the agent builder wants to connect an OAuth account during agent setup, so that all users of the agent share the same credentials. After the user authorizes, the OAuth callback stores credentials temporarily. Use `:consumeOAuthCredentials` to finalize and create the auth record.
Consumes temporarily stored OAuth credentials from a completed application-level OAuth flow and creates an `IntegrationAuth` record bound to the specified integration config.
The credential key is returned to the frontend via the OAuth success redirect after the user completes authorization. The resulting connection is shared by every agent that references the target config. The credential key is single-use.