Returns the Zero Trust edge services the caller's org owns.
Returns the Zero Trust edge services the caller's org owns.
GET /v1/network/services
| Address | https://api.hanzo.ai/v1/network/services |
| Method | GET |
| Operation | get_network_services |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns the Zero Trust edge services the caller's org owns.
One row per real ZT edge service tagged with the org's "org-<org>" role attribute: mtls is "required" when the service mandates end-to-end encryption and "enabled" otherwise (the fabric always mutually authenticates every link), and status is "active" because a listed service is a configured, dialable entry. A service tagged for another org, or tagged for none, is invisible here.
Unlike the network and router reads this does NOT degrade: an unconfigured deployment answers 503 and an unreachable controller surfaces the upstream's status, so a mesh page never renders "no services" for a fabric it simply could not read.
Request
GET /v1/network/services takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | meshServiceList | ok |
200 body — 5 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
services | body | meshView[] | — | Services is one row per ZT edge service tagged with the caller's org role. |
services[].id | body | string | — | ID is the ZT edge service's id. |
services[].mtls | body | string | — | Mtls is "required" when the service mandates end-to-end encryption, else "enabled" — the fabric mutually authenticates every link, so it is never truly off. |
services[].service | body | string | — | Service is the edge service's name. |
services[].status | body | string | — | Status is "active": a listed service is a configured, dialable mesh entry. |
Failure carries the platform error shape — see Errors.
Examples
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, NetworkApi } from 'hanzoai';
const api = new NetworkApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getNetworkServices();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import NetworkApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = NetworkApi(client).get_network_services()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.NetworkAPI.GetNetworkServices(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, network_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = network_api::get_network_services(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.NetworkApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new NetworkApi(client).getNetworkServices();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/network/services \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches network through the zt tool, which names its 4 operations with its own verbs — this one among them, under a name only the door 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_mesh_services"
}
}
}'How is this guide?