Sets a campaign's send time and moves it to "scheduled".

POST /v1/marketing/campaigns/{id}/schedule

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


Address	`https://api.hanzo.ai/v1/marketing/campaigns/{id}/schedule`
Method	`POST`
Operation	`post_marketing_campaigns_by_id_schedule`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Sets a campaign's send time and moves it to "scheduled". A scheduledAt of 0 clears the schedule and returns it to "draft".

Request

3 fields, body application/json (required).

Field	In	Type	Required	Description
`id`	path	string	yes	ID is the campaign id from the path.
`id`	body	string	—	ID is the campaign id from the path.
`scheduledAt`	body	integer	—	ScheduledAt is the unix send time.

Response

Status	Body	Meaning
`200`	Campaign	ok

200 body — 10 fields.

Field	In	Type	Always	Description
`budget`	body	integer	—	Budget is what the campaign is allowed to cost, in USD cents.
`channel`	body	string	—	Channel is the delivery surface: email, sms, social, meta, google or tiktok.
`createdAt`	body	integer	—	CreatedAt is unix seconds when the campaign was registered.
`id`	body	string	—	ID is the server-assigned campaign id ("camp_" + 128 random bits).
`name`	body	string	—	Name is the campaign's label.
`objective`	body	string	—	Objective is the free-text goal ("signups"), capped at 1024 bytes.
`scheduledAt`	body	integer	—	ScheduledAt is the unix send time; 0 means unscheduled.
`spend`	body	integer	—	Spend is what the campaign has cost so far, in USD cents, clamped to >= 0.
`status`	body	string	—	Status is the lifecycle: draft, scheduled, active, paused or completed.
`updatedAt`	body	integer	—	UpdatedAt is unix seconds of the last write.

Failure carries the platform error shape — see Errors.

Examples

hanzo marketing campaigns schedule <id>

import { Configuration, MarketingApi } from 'hanzoai';

const api = new MarketingApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postMarketingCampaignsByIdSchedule({ id: 'id', id: "<id>", scheduledAt: 0 });

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_campaigns_by_id_schedule(id='id', id="<id>", scheduled_at=0)

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

resp, _, err := client.MarketingAPI.PostMarketingCampaignsByIdSchedule(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_campaigns_by_id_schedule(&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).postMarketingCampaignsByIdSchedule();

curl -X POST https://api.hanzo.ai/v1/marketing/campaigns/<id>/schedule \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "id": "<id>",
       "scheduledAt": 0
     }'

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

Sets a campaign's send time and moves it to "scheduled".

Request

Response

Examples

On this page