Try our new Setup Skill to automatically integrate Hyperspell into your project
curl --request GET \
--url https://api.hyperspell.com/integrations/{integration_id}/channels \
--header 'Authorization: Bearer <token>'{
"channels": [
{
"id": "<string>",
"name": "<string>",
"type": "channel"
}
],
"selected": [
"<string>"
]
}List available channels/chats for a connected integration.
Also returns the connection’s currently-selected IDs so a picker can render the right boxes pre-checked without a second round trip.
curl --request GET \
--url https://api.hyperspell.com/integrations/{integration_id}/channels \
--header 'Authorization: Bearer <token>'{
"channels": [
{
"id": "<string>",
"name": "<string>",
"type": "channel"
}
],
"selected": [
"<string>"
]
}Documentation Index
Fetch the complete documentation index at: https://docs.hyperspell.com/llms.txt
Use this file to discover all available pages before exploring further.
API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.
The connection ID to use for listing channels
For hierarchical providers (e.g. Microsoft Teams): omit to list root containers (workspaces); pass a container's id to list its children (sub-channels). Selected ids in the response always reflect the leaf values stored in user_options.channels regardless of which level is queried.
Was this page helpful?