Publishes a post NOW, synchronously, whatever its schedule.

POST /v1/marketing/calendar/{id}/publish

Marketing → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/marketing/calendar/{id}/publish`
Method	`POST`
Operation	`post_marketing_calendar_by_id_publish`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Publishes a post NOW, synchronously, whatever its schedule. No social connector is wired today, so every channel answers an honest 501 naming the seam a real one would plug into, and the post is recorded failed with that exact reason — never a faked "published".

Request

1 field.

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the post id from the path, as returned by create.

Response

Status	Body	Meaning
`200`	CalendarPost	ok

200 body — 10 fields.

Field	In	Type	Always	Description
`body`	body	string	—	Body is the post text.
`channel`	body	string	—	Channel is the target network: x, facebook, instagram, linkedin, tiktok, youtube or threads.
`createdAt`	body	integer	—	CreatedAt is unix seconds when the post was added, server-assigned and never rewritten.
`error`	body	string	—	Error is the exact reason the last publish attempt failed — the honest record behind a "failed" status, never a faked success.
`id`	body	string	—	ID is the server-assigned post id ("cal_" + 128 random bits).
`publishedAt`	body	integer	—	PublishedAt is when the publish succeeded; 0 until it does.
`scheduledAt`	body	integer	—	ScheduledAt is the unix publish time; 0 leaves the post a draft, and any value makes it "scheduled" for the durable sweep to pick up.
`status`	body	string	—	Status is draft, scheduled, published, failed or canceled.
`title`	body	string	—	Title is the post's internal label, capped at 1024 bytes.
`updatedAt`	body	integer	—	UpdatedAt is unix seconds of the last write, server-assigned.

Failure carries the platform error shape — see Errors.

Examples

hanzo marketing calendar publish <id>

import { Configuration, MarketingApi } from 'hanzoai';

const api = new MarketingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postMarketingCalendarByIdPublish({ id: 'id' });

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = MarketingApi(client).post_marketing_calendar_by_id_publish(id='id')

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

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

use hanzo_cloud::apis::{configuration::Configuration, marketing_api};

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

let result = marketing_api::post_marketing_calendar_by_id_publish(&cfg, Default::default()).await?;

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

ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));

var result = new MarketingApi(client).postMarketingCalendarByIdPublish();

curl -X POST https://api.hanzo.ai/v1/marketing/calendar/<id>/publish \
  -H "Authorization: Bearer $HANZO_API_KEY"

The door reaches marketing through the marketing tool, which names its 35 operations with its own verbs — this one among them, under a name only the door 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": "list_marketing_audiences"
         }
       }
     }'

Marketing API · All Hanzo APIs · Interactive reference

Publishes a post NOW, synchronously, whatever its schedule.

Request

Response

Examples

On this page