# List runs — GET /v1/auto/automations/{id}/runs URL: https://docs.hanzo.ai/docs/openapi/auto/get-auto-automations-by-id-runs > Returns one automation's runs, newest first, to the person it runs as or an admin of the org. `GET /v1/auto/automations/{id}/runs` > [Auto →](https://docs.hanzo.ai/docs/openapi/auto) · [All API references →](https://docs.hanzo.ai/docs/openapi) · [Get started →](https://docs.hanzo.ai/docs/guides) | | | | ------------- | ---------------------------------------------------- | | **Address** | `https://api.hanzo.ai/v1/auto/automations/{id}/runs` | | **Method** | `GET` | | **Operation** | `get_auto_automations_by_id_runs` | | **Auth** | `Authorization: Bearer $HANZO_API_KEY` | Returns one automation's runs, newest first, to the person it runs as or an admin of the org. Each links the Dev run it started as `transcript`. The optional `limit` bounds the page. ## Request 2 fields. | Field | In | Type | Required | Description | | ------- | ----- | ------- | -------- | -------------------------------------------------- | | `id` | path | string | yes | ID is the automation, from the path. | | `limit` | query | integer | — | Limit bounds the page (default 200, maximum 1000). | ## Response | Status | Body | Meaning | | --------- | ---------------------- | ------- | | `200` | auto.automationRunPage | ok | | `default` | problem-details | refused | `200` body — 12 fields. | Field | In | Type | Always | Description | | ---------------------- | ---- | --------------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `data` | body | auto.AutomationRun\[] | — | Data is the automation's runs, newest first. | | `data[].at` | body | string | — | At is when it started and Finished when it ended (null while it runs), RFC 3339 UTC. | | `data[].draft` | body | string | — | Draft is the post the agent wrote, for an automation that posts; empty otherwise. | | `data[].finished` | body | string | — | | | `data[].id` | body | string | — | | | `data[].posts` | body | auto.PostResult\[] | — | Posts are where it went: one per account, its link or the platform's reason it did not go. | | `data[].posts[].error` | body | string | — | Error is the platform's reason it did not go; absent when it did. | | `data[].posts[].to` | body | string | — | To is the account's platform: x, linkedin or facebook. | | `data[].posts[].url` | body | string | — | URL opens the post; absent when it did not go. | | `data[].status` | body | string | — | Status is succeeded, failed, running, queued, review for a post waiting for its person to post or discard it, skipped for a start that found the previous run still going, or refused for a run whose person is no longer a member of the org. | | `data[].summary` | body | string | — | Summary is one line on how it went. | | `data[].transcript` | body | string | — | Transcript opens the run's Dev run; null when it started none. | Failure carries the platform error shape — see [Errors](https://docs.hanzo.ai/docs/errors). ## Examples **CLI** `hanzo` has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK. **SDK** **.ts** ```ts import { Configuration, AutoApi } from 'hanzoai'; const api = new AutoApi(new Configuration({ accessToken: process.env.HANZO_API_KEY })); const { data } = await api.getAutoAutomationsByIdRuns({ id: 'id' }); ``` **.py** ```python 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_automations_by_id_runs(id='id') ``` **.go** ```go cfg := hanzoai.NewConfiguration() cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY")) client := hanzoai.NewAPIClient(cfg) resp, _, err := client.AutoAPI.GetAutoAutomationsByIdRuns(context.Background()).Execute() if err != nil { return err } ``` **.rs** ```rust 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_automations_by_id_runs(&cfg, Default::default()).await?; ``` **.java** ```java 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).getAutoAutomationsByIdRuns(); ``` **HTTP** ```bash curl https://api.hanzo.ai/v1/auto/automations//runs \ -H "Authorization: Bearer $HANZO_API_KEY" ``` **MCP** 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: ```bash 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](https://docs.hanzo.ai/docs/openapi/auto) · [All Hanzo APIs](https://docs.hanzo.ai/docs/openapi) · [Interactive reference](https://docs.hanzo.ai/docs/openapi/reference)