Hanzo Docs
Sign inAPI key

List jobs

Lists everything of yours that runs without you watching, across every product: each run of your automations and workflows, and every Studio render, long video or other background run a product recorded for you.

GET /v1/auto/jobs

Auto → · All API references → · Get started →

Addresshttps://api.hanzo.ai/v1/auto/jobs
MethodGET
Operationget_auto_jobs
AuthAuthorization: Bearer $HANZO_API_KEY

Lists everything of yours that runs without you watching, across every product: each run of your automations and workflows, and every Studio render, long video or other background run a product recorded for you. Each is in one of five states — scheduled, running, succeeded, failed, cancelled — with what it made (Library item ids) and what it cost when that is known. Another member's jobs are never listed.

Request

3 fields.

FieldInTypeRequiredDescription
productquerystring—Product keeps one product's jobs: chat, dev, studio or workflow.
statequerystring—State keeps one state: scheduled, running, succeeded, failed or cancelled.
limitqueryinteger—Limit bounds the page (default 100, at most 500).

Response

StatusBodyMeaning
200auto.jobPageok
defaultproblem-detailsrefused

200 body — 19 fields.

FieldInTypeAlwaysDescription
databodyauto.Job[]—Data are your jobs, the most recently changed first.
data[].automationbodystring—
data[].costbodyinteger (int64)—
data[].errorbodystring—
data[].finishedbodystring—
data[].idbodystring—
data[].kindbodystring—
data[].originbodystring—
data[].outputsbodystring[]—
data[].productbodystring—
data[].progressbodynumber (double)—
data[].refbodystring—
data[].sessionbodystring—
data[].startedbodystring—
data[].statebodystring—
data[].statusbodystring—
data[].summarybodystring—
data[].titlebodystring—
data[].updatedbodystring—

Failure carries the platform error shape — see Errors.

Examples

hanzo auto jobs list
import { Configuration, AutoApi } from 'hanzoai';

const api = new AutoApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getAutoJobs();
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_jobs()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.AutoAPI.GetAutoJobs(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_jobs(&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).getAutoJobs();
curl https://api.hanzo.ai/v1/auto/jobs \
  -H "Authorization: Bearer $HANZO_API_KEY"

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

Auto API · All Hanzo APIs · Interactive reference

Was this page useful?
Broken link or missing step? Drop it in #docs on Discord or open a PR.
PreviousGet jobsNextList provider