---
title: "List the link infrastructure keys in use"
method: GET
path: "/link/mablnet/infrastructure-keys"
tags: ["LinkMablnet"]
---

# List the link infrastructure keys in use

`GET /link/mablnet/infrastructure-keys`

Operator-only: every dedicated link infrastructure key currently assigned to a company (`Company.link_infrastructure_key`), plus the shared cluster's key (`mabl`), each with its derived carrier FQDNs and holder company ids. Fleet tooling (mops) fans cluster-scoped operations out over this list, and the decommission runbook verifies a key has zero holders before removing its terraform `clusters` entry. See dedicated-link-infra.md in link/mablnet/docs.

## Response `200`

The keys in use.

- MablnetInfrastructureKeysResponse — The link infrastructure keys in use across the deployment.
  - `keys` MablnetInfrastructureKey[]
    - `key` string — The cluster key (`mabl` = the shared multi-tenant cluster).
    - `wss_fqdn` string — Derived WSS carrier hostname (`<key>-wss.<domain>`). Absent when the deployment has no mablnet domain configured.
    - `quic_fqdn` string — Derived QUIC carrier hostname (`<key>-quic.<domain>:443`). Absent when the deployment has no mablnet domain configured.
    - `company_ids` string[] — Companies holding this key (empty for `mabl` — shared-cluster residency is the keyless default, not an assignment).

## Other responses

- `401` — User not authenticated
- `403` — User not authorized
- `default` — Unknown error

---

[API](https://skmtc.net/mabl/apis/mabl-api.md) · [All operations](https://skmtc.net/mabl/apis/mabl-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mabl/mabl-api/revisions/d0fc0114da66/schema)