List channels

Lists the distribution channels the caller's org has connected — the social integrations a publish can target.

GET /v1/content/channels

Content → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/content/channels`
Method	`GET`
Operation	`get_content_channels`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Lists the distribution channels the caller's org has connected — the social integrations a publish can target. A deployment with no distribution edge wired answers 503 rather than an empty list that would read as "no channels".

Request

GET /v1/content/channels takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	content.channelList	ok
`default`	problem-details	refused

200 body — 5 fields.

Field	In	Type	Always	Description
`data`	body	content.Channel[]	—	Data is every social channel the caller's org has connected, disabled ones included (Disabled says which).
`data[].disabled`	body	boolean	—	Disabled is true for a channel the org switched off at the social edge.
`data[].id`	body	string	—	ID is the social integration id a post targets.
`data[].name`	body	string	—	Name is the account label as the org connected it — the handle a human recognises.
`data[].provider`	body	string	—	Provider is the network behind the integration: "x", "instagram", "tiktok" and the rest of what the org connected.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo content channels

.ts

.py

.go

.rs

.java

import { Configuration, ContentApi } from 'hanzoai';

const api = new ContentApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getContentChannels();

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ContentApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ContentApi(client).get_content_channels()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ContentAPI.GetContentChannels(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::apis::{configuration::Configuration, content_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = content_api::get_content_channels(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.ContentApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new ContentApi(client).getContentChannels();

curl https://api.hanzo.ai/v1/content/channels \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches content through the content tool, which names its 6 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "get_content_board"
         }
       }
     }'

Content API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList board NextList lifecycle