sz website-routes get <route-id>
Scheduler Zero CLI website-routes get: read website activation status, exact dns instructions and history. Usage, options, examples, output and authorization.
# sz website-routes get <route-id>
The `sz website-routes get` command is part of the [Scheduler Zero CLI](/cli). Reads one website route and its activation status, DNS instructions and history in the selected workspace. The route UUID and workspace UUID are validated before dispatch. This read does not configure DNS, request a check, activate a route or retire provider resources.
## Usage
```bash
sz website-routes get <route-id> --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 get 33333333-3333-4333-8333-333333333333 --workspace 11111111-1111-4111-8111-111111111111 --json
```
## Output and side effects
The websiteRoutes.get detail response. Use returned record-aware DNS instructions instead of assuming a certificate record exists. A due check or generic check error is not evidence of provider failure or handler execution. Missing or inaccessible routes return a nonzero failure.
## 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.get`
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
[List website routes](/cli/commands/website-routes-list) · [Authorization](/authentication) · [JSON output](/cli/reference)
[All CLI commands](/cli/commands) · [Troubleshooting](/cli/troubleshooting) · [This command as Markdown](/cli/commands/website-routes-get.md) · [CLI LLM index](/cli/llms.txt)
Scheduler Zero