List tls

Returns the caller org's ACME intent together with the edge-wide TLS facts it lands in: which role this instance runs in, whether its listeners are bound, every host the ACME HostPolicy will issue a certificate for (the union across ALL orgs of TLS-marked routes and configured extraHosts, because one process holds one certificate cache), and the ACME directory and account email the process was started with.

GET /v1/ingress/tls

Addresshttps://api.hanzo.ai/v1/ingress/tls
MethodGET
Operationget_ingress_tls
AuthAuthorization: Bearer $HANZO_API_KEY

Returns the caller org's ACME intent together with the edge-wide TLS facts it lands in: which role this instance runs in, whether its listeners are bound, every host the ACME HostPolicy will issue a certificate for (the union across ALL orgs of TLS-marked routes and configured extraHosts, because one process holds one certificate cache), and the ACME directory and account email the process was started with.

Request

GET /v1/ingress/tls takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200ingress.ingressTLSok
defaultproblem-detailsrefused

200 body — 10 fields.

FieldInTypeAlwaysDescription
acmeDirectorybodystring—ACMEDirectory is the ACME endpoint in use: the staging URL, or "letsencrypt-production".
acmeEmailbodystring—ACMEEmail is the account email the PROCESS was started with (CLOUD_INGRESS_ACME_EMAIL), not the stored config's.
configbodyingress.TLSConfig—
config.acmeEmailbodystring—ACMEEmail is the ACME account email.
config.extraHostsbodystring[]—ExtraHosts get certificates without owning a route — at most 256.
config.stagingbodyboolean—Staging issues from Let's Encrypt's staging directory (untrusted certs, high rate limits).
edgeEnabledbodyboolean—EdgeEnabled is true when the edge listeners are actually bound.
managedHostsbodystring[]—ManagedHosts is every host the ACME HostPolicy will issue a certificate for — the union across ALL orgs of TLS-marked routes and configured extraHosts, because one process holds one certificate cache.
notebodystring—Note states which fields hot-apply and which need an edge restart.
rolebodystring—Role is "edge" when this instance binds the listeners, else "app".

Failure carries the platform error shape — see Errors.

Examples

hanzo ingress tls get
import { Configuration, IngressApi } from 'hanzoai';

const api = new IngressApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getIngressTls();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IngressApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IngressApi(client).get_ingress_tls()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.IngressAPI.GetIngressTls(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, ingress_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = ingress_api::get_ingress_tls(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IngressApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new IngressApi(client).getIngressTls();
curl https://api.hanzo.ai/v1/ingress/tls \
  -H "Authorization: Bearer $HANZO_API_KEY"

Tool ingress, op get_ingress_tls — POST the JSON-RPC envelope to https://api.hanzo.ai/v1/mcp.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "ingress",
         "arguments": {
           "op": "get_ingress_tls",
           "input": {}
         }
       }
     }'

Ingress API · All Hanzo APIs · Interactive reference

Was this page useful?