List templates

Returns the starter automations: a name, what it does, the instructions it runs and the schedule it suggests, in the caller's own zone.

GET /v1/auto/templates

Auto → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/auto/templates`
Method	`GET`
Operation	`get_auto_templates`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Returns the starter automations: a name, what it does, the instructions it runs and the schedule it suggests, in the caller's own zone.

Request

GET /v1/auto/templates takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	auto.starterPage	ok
`default`	problem-details	refused

200 body — 12 fields.

Field	In	Type	Always	Description
`data`	body	auto.Starter[]	—	Data is the starters.
`data[].description`	body	string	—
`data[].icon`	body	string	—
`data[].instructions`	body	string	—
`data[].key`	body	string	—
`data[].name`	body	string	—
`data[].schedule`	body	auto.Schedule	—
`data[].schedule.at`	body	string	—	At is the local time, HH:MM on a 24-hour clock, for daily, weekdays and weekly.
`data[].schedule.cron`	body	string	—	Cron is a five-field cron expression (minute hour day-of-month month day-of-week), for kind cron only, read in TZ.
`data[].schedule.day`	body	string	—	Day is the weekday a weekly schedule runs on: mon, tue, wed, thu, fri, sat or sun.
`data[].schedule.kind`	body	string	—	Kind is manual, hourly, daily, weekdays, weekly or cron.
`data[].schedule.tz`	body	string	—	TZ is the IANA time zone every time here is read in.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

.ts

.py

.go

.rs

.java

import { Configuration, AutoApi } from 'hanzoai';

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

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = AutoApi(client).get_auto_templates()

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

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

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

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

let result = auto_api::get_auto_templates(&cfg, Default::default()).await?;

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

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

var result = new AutoApi(client).getAutoTemplates();

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

MCP reaches auto through the auto tool, which names its 14 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": "list_auto_flows"
         }
       }
     }'

Auto API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousList runs — GET /v1/auto/runs NextUpdate automations