Loading sz website-routes list
sz website-routes list

Scheduler Zero CLI website-routes list: list website activation stage, scheduling and unconfirmed execution status. Usage, options, examples, output and authorization.
# sz website-routes list

The `sz website-routes list` command is part of the [Scheduler Zero CLI](/cli). Reads website routes in the selected workspace without changing DNS, activation or scheduling. Each activationStatus separates the last checkpoint, scheduling eligibility, health freshness and unobserved execution. A check being due is not proof that a handler started or failed.

## Usage

```bash
sz website-routes list --workspace <id> [options]
```

If you have not installed `sz` globally, replace `sz` in the usage above with `npx --yes @scheduler-zero/sz@latest` or `bunx @scheduler-zero/sz@latest`, preserving the arguments and options. See [installation](/cli/installation).

## Options

| Option | Meaning |
| --- | --- |
| `--workspace <id>` | Workspace id for workspace-scoped commands |
| `--api-key <key>` | API key (prefer SCHEDULER_ZERO_API_KEY) |
| `--base-url <url>` | API origin (default: https://api.schedulerzero.com) |
| `--json` | Emit machine-readable JSON |
| `--format table\|json` | Select output format |
| `-h, --help` | Show this help |

## Examples

The UUIDs below are illustrative; use IDs from your own visible workspaces and campaigns.

```bash
sz website-routes list --workspace 11111111-1111-4111-8111-111111111111 --json
```

## Output and side effects

The websiteRoutes.list response with route IDs and activationStatus. Object responses remain JSON in the default format. Execution and freshness remain explicitly unknown when durable evidence is absent; no attempt timestamp or ETA is invented.

## Authorization

Requires a valid credential with website-route read access in the selected workspace within its restrictions and the owner authority. Route IDs do not authorize writes or bypass workspace ownership.

## Underlying operations

- `websiteRoutes.list`

Browser issuance stays a human-approved handoff where applicable; the command does not bypass that boundary. The exact product operation schemas are in [OpenAPI](/openapi.json) and [the REST Markdown reference](/rest-api/reference.md). For broader capabilities, use [MCP tools](/mcp/tools).

## Related documentation

[Read one website route](/cli/commands/website-routes-get) · [Workspace discovery](/cli/commands/workspaces-list) · [REST schemas](/rest-api/reference)

[All CLI commands](/cli/commands) · [Troubleshooting](/cli/troubleshooting) · [This command as Markdown](/cli/commands/website-routes-list.md) · [CLI LLM index](/cli/llms.txt)