Registers a new ad campaign for the caller's org and answers 201 with the…

Registers a new ad campaign for the caller's org and answers 201 with the stored row.

POST /v1/ad/campaigns

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


Address	`https://api.hanzo.ai/v1/ad/campaigns`
Method	`POST`
Operation	`post_ad_campaigns`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Registers a new ad campaign for the caller's org and answers 201 with the stored row. It only records the campaign — nothing is sent to the ad network until POST /v1/ad/campaigns/{id}/launch runs it. The org is stamped by the server from the validated principal, so a body can never place a campaign in another tenant.

Request

7 fields, body application/json (required).

Field	In	Type	Required	Description
`account`	body	string	—	Account is the provider ad-account this campaign runs on (Meta act_<id>).
`budget`	body	integer	—	Budget is the campaign budget in MINOR units (cents).
`name`	body	string	—	Name is the campaign's display label.
`objective`	body	string	—	Objective is the campaign goal as the provider names it.
`platform`	body	string	—	Platform is the ad network: meta, google, tiktok or x.
`spend`	body	integer	—	Spend is the amount spent so far in MINOR units (cents).
`status`	body	string	—	Status is the lifecycle state: draft, active, paused or completed.

Response

Status	Body	Meaning
`201`	AdCampaign	created

201 body — 11 fields.

Field	In	Type	Always	Description
`account`	body	string	—	Account is the provider ad-account the campaign runs under, in Meta's act_<id> form.
`budget`	body	integer	—	Budget is the campaign's authorized spend in MINOR units (cents). Negative clamps to 0.
`createdAt`	body	integer	—	CreatedAt is when the campaign was first stored, in unix seconds.
`externalId`	body	string	—	ExternalID is the ad network's own campaign id, written by a successful launch and by nothing else — an update never touches it.
`id`	body	string	—	ID is the campaign's server-minted handle, "camp_" + 32 hex.
`name`	body	string	—	Name is the campaign's display label, and the name Meta creates the campaign object under at launch.
`objective`	body	string	—	Objective is the campaign goal spelled as the provider names it ("conversions", "OUTCOME_TRAFFIC"), passed through to the network verbatim at launch — Meta…
`platform`	body	string	—	Platform is the ad network: meta, google, tiktok or x, and nothing else — a write naming another is 400. Empty stores as meta.
`spend`	body	integer	—	Spend is spend-to-date in MINOR units (cents), as last written through create or update. Negative clamps to 0.
`status`	body	string	—	Status is the lifecycle: draft, active, paused or completed, and nothing else — a write naming another is 400.
`updatedAt`	body	integer	—	UpdatedAt is when the row was last written, in unix seconds — set by create, update and launch.

Failure carries the platform error shape — see Errors.

Examples

hanzo ads campaigns create

import { Configuration, AdApi } from 'hanzoai';

const api = new AdApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postAdCampaigns({ account: "<account>", budget: 0 });

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AdApi(client).post_ad_campaigns(account="<account>", budget=0)

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

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

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

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

let result = ad_api::post_ad_campaigns(&cfg, Default::default()).await?;

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

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

var result = new AdApi(client).postAdCampaigns();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

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

The door reaches ad through the ads tool, which names its 7 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_ads_campaigns"
         }
       }
     }'

Ad API · All Hanzo APIs · Interactive reference

Registers a new ad campaign for the caller's org and answers 201 with the…

Request

Response

Examples

On this page