List board

Aggregates the caller org's marketing content across every publishable content type into ONE queue board — the cross-type read the framework's per-DocType list cannot give.

GET /v1/content/board

Content → · All API references → · Get started →

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

Aggregates the caller org's marketing content across every publishable content type into ONE queue board — the cross-type read the framework's per-DocType list cannot give. It never fails on a partial outage: a content type the org has not installed, or one whose search errors, is skipped and logged rather than failing the whole board.

Request

4 fields.

Field	In	Type	Required	Description
`status`	query	string	—	Status keeps only items in one lifecycle state (draft, in_review, approved, queued, published, archived).
`project`	query	string	—	Project keeps only items in one brand/site sub-scope.
`doctype`	query	string	—	DocType keeps only one content type; omitted, the board spans every publishable type.
`limit`	query	integer	—	Limit caps the rows returned, clamped to 1000.

Response

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

200 body — 8 fields.

Field	In	Type	Always	Description
`count`	body	integer (int64)	—	Count is the number of rows in THIS page — never the org's total.
`data`	body	content.boardItem[]	—	Data is the matching items, most recently updated first.
`data[].doctype`	body	string	—	DocType is which content type the row came from: Campaign, SocialPost or Asset.
`data[].name`	body	string	—	Name is the document within that type.
`data[].project`	body	string	—	Project is the brand/site sub-scope within the org.
`data[].status`	body	string	—	Status is the lifecycle state: draft, in_review, approved, queued, published or archived.
`data[].title`	body	string	—	Title is the item's headline, read from its type's own title field.
`data[].updatedAt`	body	integer (int64)	—	UpdatedAt is unix seconds of the document's last write, and the key the board sorts on, newest first.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo content board

.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.getContentBoard();

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_board()

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

resp, _, err := client.ContentAPI.GetContentBoard(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_board(&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).getContentBoard();

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

Tool content, op get_content_board — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.

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

Content API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousDelete agent NextList channels